-
Notifications
You must be signed in to change notification settings - Fork 14
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
Make parsing errors type-safe #75
Milestone
Comments
chuwy
changed the title
Add column name to error message
Add column name to decoding error message
May 5, 2019
chuwy
changed the title
Add column name to decoding error message
Make parsing errors type-safe
Jul 5, 2019
This was referenced Jul 5, 2019
aldemirenes
added a commit
that referenced
this issue
Jul 8, 2019
aldemirenes
added a commit
that referenced
this issue
Aug 13, 2019
aldemirenes
added a commit
that referenced
this issue
Aug 14, 2019
aldemirenes
added a commit
that referenced
this issue
Aug 15, 2019
dilyand
pushed a commit
that referenced
this issue
Nov 4, 2019
dilyand
added a commit
that referenced
this issue
Nov 4, 2019
dilyand
added a commit
that referenced
this issue
Nov 4, 2019
dilyand
pushed a commit
that referenced
this issue
Nov 4, 2019
dilyand
pushed a commit
that referenced
this issue
Nov 6, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current example for
{}
in place ofunstruct_event
:The text was updated successfully, but these errors were encountered: