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

Decode: fix error reporting of type mismatch on inline tables #853

Merged
merged 1 commit into from
Feb 28, 2023

Conversation

pelletier
Copy link
Owner

Parser did not track the location of the faulty inline table in the document, and unmarshaler tried to the use the non-raw data field of the AST node, both resulting into a panic when generating the parser error.

Fixes #850

Parser did not track the location of the faulty inline table in the
document, and unmarshaler tried to the use the non-raw data field of the
AST node, both resulting into a panic when generating the parser error.

Fixes #850
@pelletier pelletier added the bug Issues describing a bug in go-toml. label Feb 28, 2023
@pelletier pelletier changed the title Fix error report of type mismatch on inline tables Fix error reporting of type mismatch on inline tables Feb 28, 2023
@pelletier pelletier merged commit 8a416da into v2 Feb 28, 2023
@pelletier pelletier deleted the issue-850 branch February 28, 2023 16:06
@pelletier pelletier changed the title Fix error reporting of type mismatch on inline tables Decode: fix error reporting of type mismatch on inline tables Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues describing a bug in go-toml.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

v2: panic unmarshaling inline table to string
1 participant