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

Proposal to improve errors #122

Merged
merged 2 commits into from
Apr 8, 2024
Merged

Proposal to improve errors #122

merged 2 commits into from
Apr 8, 2024

Conversation

asofter
Copy link
Contributor

@asofter asofter commented Mar 26, 2024

Introducing a new way to handle errors which I want to expand to skips and issues if this is approved. The issue is that with enum it's hard to extend errors when customizing modelscan, because you will always need to change the main Enum class. However, with this new way, error can be easily extended to any needs.

@asofter asofter requested a review from iamfaisalkhan March 26, 2024 14:00
Copy link
Member

@iamfaisalkhan iamfaisalkhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Error classes are simplifying creating errors.

@iamfaisalkhan iamfaisalkhan merged commit d5f289c into main Apr 8, 2024
8 checks passed
@iamfaisalkhan iamfaisalkhan deleted the model-object-errors branch April 8, 2024 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants