-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCANNPM-39 exit parent process w correct exit code #153
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I realize now that adding process.exit(..)
either on top-level or the one when running the Scanner Engine will break the JS API, eg an user who calls
await scan({ .. })
scanWithCallback({..}, (error) => { .. })
Will have his program shutting down immediately, but that's not what we want to do! - See runner.ts
1a9df8c
to
2ed7725
Compare
d60a005
to
c0ebaec
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with FV ✅
c0ebaec
to
20af54c
Compare
Quality Gate passedIssues Measures |
Hello, thanks for fixing this issue. Could you please create a release and publish a new version to NPM? (asking, because 4.1.0 wasn't published on NPM) |
Could you please share your plans about when it will be released? |
No description provided.