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.

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

Use dedicated exception types for set and parse errors #510

Closed
jklmnn opened this issue Nov 30, 2020 · 0 comments · Fixed by #542
Closed

Use dedicated exception types for set and parse errors #510

jklmnn opened this issue Nov 30, 2020 · 0 comments · Fixed by #542
Assignees
Labels
bug pyrflx Related to pyrflx package (Legacy Python API)

Comments

@jklmnn
Copy link
Member

jklmnn commented Nov 30, 2020

Currently PyRFLX uses python exceptions to indicate errors. This breaks the ability to distinguish between errors due to invalid input data and errors in the library. To fix this all exceptions due to invalid input data should throw dedicated exceptions for parsing or setting fields.

@jklmnn jklmnn created this issue from a note in RecordFlux 0.5 (To do) Nov 30, 2020
@jklmnn jklmnn added bug pyrflx Related to pyrflx package (Legacy Python API) labels Nov 30, 2020
rssen added a commit that referenced this issue Jan 4, 2021
rssen added a commit that referenced this issue Jan 6, 2021
@treiher treiher moved this from To do to Done in RecordFlux 0.5 Jan 7, 2021
rssen added a commit that referenced this issue Jan 12, 2021
RecordFlux 0.5 automation moved this from Done to Merged Jan 13, 2021
rssen added a commit that referenced this issue Jan 13, 2021
@treiher treiher mentioned this issue Aug 4, 2021
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug pyrflx Related to pyrflx package (Legacy Python API)
Projects
No open projects
RecordFlux 0.5
  
Merged
Development

Successfully merging a pull request may close this issue.

2 participants