We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In src/cli.js the program errors are written out with console.log.
Consider using console.error instead so that stderr and stdout can be redirected separately.
Like in my case I only want the the swagger output written to a file, and if there is a parsing error, I'd like to see that in the shell.
swagger-inline "./*.js" --base 'swaggerBase.json' 2>&1 > api.json
.catch(err => { - console.log('An error occured:'); - console.log(err); + console.log('An error occured:'); + console.log(err); process.exit(-1); });
The text was updated successfully, but these errors were encountered:
@Morten1337 If you're up for submitting a pull request we'll happily pull it in.
Sorry, something went wrong.
Done in #179
No branches or pull requests
In src/cli.js the program errors are written out with console.log.
Consider using console.error instead so that stderr and stdout can be redirected separately.
Like in my case I only want the the swagger output written to a file, and if there is a parsing error, I'd like to see that in the shell.
The text was updated successfully, but these errors were encountered: