Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork437
Improve error messages by including the path#356
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Without the path users need to search all their code for a malformedpath or debug to find the issueCloses:pillarjs#336
Tried a couple of different places to include the path in the error message and I think prepending it is the easiest to read but if you'd like it somewhere else I'd update accordingly |
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 appreciate this PR, it's a great direction! However I think it'd be good to avoid usingstringify
as it can output a different path to the original input, and instead add aoriginalPath
or something toTokenData
. I can open a PR you can review if that's OK?
Without the path users need to search all their code for a malformed path or debug to find the issue
Closes:#336