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
It would be great to be able to get results of initCommands execution - to check for errors and throw if something is not right (if there's a message in stderr, for example).
The text was updated successfully, but these errors were encountered:
@dchekanov if you want to submit that in a PR I can build/tag and push it. I just don't have time to code it at the moment. Or maybe @nfedyk could do it.
I was able to inject a function to validate initCommands results. However, stderr for basic bash commands like >&2 echo "error" or err is empty. The expected stderr content ("error"/"bash: err: command not found") appears in the next command result instead for some reason, and it's deeper than I'd like to go at the moment. With pwsh it seem to work fine for post-init commands, and that's enough in our case. I'll submit a PR if our requirements change and I end up patching the library.
Hi and thanks for open-sourcing this module!
It would be great to be able to get results of
initCommands
execution - to check for errors and throw if something is not right (if there's a message in stderr, for example).The text was updated successfully, but these errors were encountered: