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

Consider refactoring errors into a dedicated data type #66

Open
anton-trunov opened this issue Oct 5, 2023 · 0 comments
Open

Consider refactoring errors into a dedicated data type #66

anton-trunov opened this issue Oct 5, 2023 · 0 comments
Assignees
@verytactical
Labels
big This is a hard task, more like a project and will take a while to implement errors Error reporting mechanism refactoring
Milestone
v1.7.0

Comments

@anton-trunov
Copy link
Member

This will make error reporting more uniform
@anton-trunov anton-trunov added the errors Error reporting mechanism label Mar 26, 2024
@anton-trunov anton-trunov added the big This is a hard task, more like a project and will take a while to implement label Apr 24, 2024
@anton-trunov anton-trunov added this to the v1.6.0 milestone Jul 26, 2024
@anton-trunov anton-trunov self-assigned this Jul 26, 2024
@anton-trunov anton-trunov modified the milestones: v1.6.0, v1.7.0 Sep 16, 2024
@verytactical verytactical mentioned this issue Dec 18, 2024
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@verytactical verytactical

Labels
big This is a hard task, more like a project and will take a while to implement errors Error reporting mechanism refactoring
Projects
None yet
Milestone
v1.7.0
Development

No branches or pull requests
2 participants
@anton-trunov @verytactical