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.

Sign up for GitHub

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

Jump to bottom

Report nom parsing failure in errors #27

Open
klingtnet opened this issue Mar 20, 2022 · 0 comments
Open

Report nom parsing failure in errors #27

klingtnet opened this issue Mar 20, 2022 · 0 comments
Labels
good first issue

Comments

@klingtnet
Copy link
Owner

klingtnet commented Mar 20, 2022 •
edited
Loading

Right now all parsing errors are translated into an OscError::ReadError or OscError::BadChar which eventually omit details stored in the nom parsing error. Nom error management provides some details.

This is a follow-up of #26 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@klingtnet