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.

Sign up for GitHub

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

Jump to bottom

Missing or invalid config file needs explicit error handling #9

Open

tarkatronic opened this issue Jan 26, 2021 · 0 comments

Labels

bug good first issue loaders

Contributor

tarkatronic commented Jan 26, 2021

Right now if you fail to specify a filename on the command line, or you point to an invalid file, you get an error along the lines of:

NOTE: This is a dry run. Actions will not actually be performed.
node:internal/process/promises:227
          triggerUncaughtException(err, true /* fromPromise */);
          ^

[Error: ENOENT: no such file or directory, open 'membership.toml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'membership.toml'
}

This should have a friendly error message telling the user that the file was not found, as opposed to a stack trace.

tarkatronic added bug good first issue labels

tarkatronic added the loaders label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment