Serve test package docs through grinder #1578
Conversation
| if (label == null) label = ''; | ||
| if (label != '') label = '-$label'; | ||
| var launcher = new SubprocessLauncher('build-test-package-docs$label'); | ||
| await launcher.runStreamed(sdkBin('pub'), ['get'], |
There was a problem hiding this comment.
I think there's a grinder shorthand for sdkBin('pub') (but don't recall what it is).
There was a problem hiding this comment.
There is indeed (a class named Pub). However grind's shorthands don't allow me to have the control I want for how they are executed. I've found it frustrating to debug a series of fork-execs that is partially hidden by "shorthands" that look like they aren't fork/execs. This way, I can see exactly what it is doing both in the output of grinder and in the source code.
| if (label == null) label = ''; | ||
| if (label != '') label = '-$label'; | ||
| var launcher = new SubprocessLauncher('build-test-package-docs$label'); | ||
| await launcher.runStreamed(sdkBin('pub'), ['get'], |
There was a problem hiding this comment.
There is indeed (a class named Pub). However grind's shorthands don't allow me to have the control I want for how they are executed. I've found it frustrating to debug a series of fork-execs that is partially hidden by "shorthands" that look like they aren't fork/execs. This way, I can see exactly what it is doing both in the output of grinder and in the source code.
tool/grind.dart
Outdated
| @Depends(buildTestPackageDocs) | ||
| Future serveTestPackageDocs() async { | ||
| log('launching dhttpd on port 8002 for SDK'); | ||
| var launcher = new SubprocessLauncher('serve-sdk-docs'); |
There was a problem hiding this comment.
this string is wrong, changed.
The test package is useful for trying things out and demoing them as docs build much faster for them.