Skip to content

Adding better error messages for JSON parsing errors #75

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

Merged
merged 2 commits into from
Jan 29, 2025

Conversation

Craigacp
Copy link
Member

Fixes #74.

@Craigacp Craigacp added the oracle employee PR is from an Oracle employee label Jan 26, 2025
@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Jan 26, 2025
Copy link
Member

@jhalexand jhalexand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One question about the message included with the exception - it assumes that if the given value was not textual then it was numerical, but I think we'd pass into the same code if, for example, an array was provided as a value in which case the message could be a little confusing. So maybe "numerical or other types are not parsed"?

@Craigacp
Copy link
Member Author

Sure, I'll fix that.

@Craigacp
Copy link
Member Author

Done

Copy link
Member

@jhalexand jhalexand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@Craigacp Craigacp merged commit 324fe89 into main Jan 29, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement. oracle employee PR is from an Oracle employee
Projects
None yet
Development

Successfully merging this pull request may close these issues.

json config files not using strings get hard to understand execption
2 participants