omicron/oas
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

Explore options for error reporting after parsing #5

New Issue
Open
opened 2025-04-02 19:56:51 +00:00 by omicron · 0 comments
omicron commented 2025-04-02 19:56:51 +00:00
Owner
Copy Link

Currently the parser just fails to parse and doesn't really keep track of where it happened. One error reporting strategy would be to keep track of the furthest point into the tokenstream we got and assume this is likely most relevant error for the user.

Currently the parser just fails to parse and doesn't really keep track of where it happened. One error reporting strategy would be to keep track of the furthest point into the tokenstream we got and assume this is likely most relevant error for the user.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
component
lexer
critical
feature
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
omicron
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: omicron/oas#5
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?