-
Notifications
You must be signed in to change notification settings - Fork 155
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
Normalize node paths in errors #229
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
782117a
Append field with expression to the path
Mingun 9f0d59b
Point to existing node instead of missing mandatory field
Mingun b811941
Add "/type" fragment to the error path of some errors in type switches
Mingun c03696c
Add "/type" or "/enum" fragment to the error path for "unable to find…
Mingun c21d54d
Fix incorrect reported path for switch types when validating types
Mingun bb717cb
Add missing `.ksy` suffix in error message to the name of file that c…
Mingun File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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'm skeptical that only the
type
key is always the culprit ofParseException
becausefromYaml2
method processes a lot of keys inside.Upon further inspection, these should be the calls that may emit
Expressions.ParseException
:kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala
Line 190 in 3a4a0e3
kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala
Lines 214 to 216 in 3a4a0e3
kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala
Lines 220 to 222 in 3a4a0e3
But even if it's always the
type
key, exceptions should be definitely handled closer to where they arise. Quite a few keys processed infromYaml2
need to parse expressions, but they normally catch it right away (as they should), e.g.:kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/ProcessExpr.scala
Lines 39 to 42 in 8913518
kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala
Line 179 in 3a4a0e3
kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/ParseUtils.scala
Lines 97 to 104 in 3a4a0e3
kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala
Lines 291 to 296 in 3a4a0e3
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.
That does not matter. You already inside
type
key here, and all other keys thatfromYaml2
processes here are subkeys of atype
.