Omit line number for toml parse error for unknown spans #2192
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the case that the span is (0..0), we don't usually know where the error really occurred. In that case just omit the line number. Resolves: greshake#2189 This error is tracked upstream: * toml: toml-rs/toml#589 * serde: serde-rs/serde#1183
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the case that the span is (0..0), we don't usually know where the error really occurred. In that case just omit the line number.
Of course the error really could be at the start of the file, but the error
unknown field XXXshould be easy enough to find and is less misleading than saying the error is on line 1, when it's not really.Resolves: #2189
This error is tracked upstream:
serde(flatten)/ enum variants toml-rs/toml#589