You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You want to see a complete synopsis of the output of the lint commands, and you might want to stop on one of them erroring, but you want to run every lint command. Whereas you want to close the other command if either the server or the test exits.
I can see a usecase for run-p --race --aggregate-output start-server integration-test where you want to ensure that the output of the server isn't interlaced, though I've just passed a "silent logging level" to servers I've used in the past with the model.
For the lint step, I feel like it would be confusing, since I reached for that option while forgetting that 0 means success, not false/error in UNIX land. I was confused about why I was only getting output from the css lint when I passed lint:css but not when I didn't pass --aggregate-output. I figured npm was overwriting previous lines somehow or something...
Probably the simplest solution though is just a README PR to just add "on success" for the less unix literate of us...
Thank you for this great tool btw, I've found it very useful over time!
The text was updated successfully, but these errors were encountered:
This might not be doable, but I'd like to suggest warning when both
--race
and--aggregate-output
are passed torun-p
.There's two situations that I'm thinking you would use these:
You want to see a complete synopsis of the output of the
lint
commands, and you might want to stop on one of them erroring, but you want to run every lint command. Whereas you want to close the other command if either the server or the test exits.I can see a usecase for
run-p --race --aggregate-output start-server integration-test
where you want to ensure that the output of the server isn't interlaced, though I've just passed a "silent logging level" to servers I've used in the past with the model.For the lint step, I feel like it would be confusing, since I reached for that option while forgetting that
0
means success, not false/error in UNIX land. I was confused about why I was only getting output from the css lint when I passedlint:css
but not when I didn't pass--aggregate-output
. I figured npm was overwriting previous lines somehow or something...Probably the simplest solution though is just a README PR to just add "on success" for the less unix literate of us...
Thank you for this great tool btw, I've found it very useful over time!
The text was updated successfully, but these errors were encountered: