Skip to content
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

Invalid input script path logs error but doesn't reject promise #43

Open
keego opened this issue Jan 3, 2017 · 0 comments
Open

Invalid input script path logs error but doesn't reject promise #43

keego opened this issue Jan 3, 2017 · 0 comments

Comments

@keego
Copy link

keego commented Jan 3, 2017

When attempting to create a schema from a file that doesn't exist, an ENOENT: no such file or directory error is logged to the console but isn't thrown. This prevents API consumers from being able to differentiate cases based on whether or not the input file path is valid, and forces consumers to verify all input paths beforehand. If this is the desired behavior, it would be nice to at least have this option configurable so that all errors can be handled by the consumer on a case-by-case basis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant