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

Unify error format #91

Open
groenroos opened this issue Dec 30, 2020 · 0 comments
Open

Unify error format #91

groenroos opened this issue Dec 30, 2020 · 0 comments
Assignees
@groenroos
Labels
enhancement Improvements to existing features and functionality low priority Issues which should only be considered after everything else is done refactoring Drastic code quality improvements
Milestone
M3 - Release 3.0

Comments

@groenroos
Copy link
Member

Currently, not all errors across the app are returned as SaplingErrors, and even SaplingError can vary wildly in its output.

Unify the format of error output by SaplingError, regardless of the input it receives. This would mean generating metadata for string-based errors, and validating the object format and filling in any gaps for object-based errors.
@groenroos groenroos added enhancement Improvements to existing features and functionality refactoring Drastic code quality improvements labels Dec 30, 2020
@groenroos groenroos added this to the M2 - Release 2.0 milestone Dec 30, 2020
@groenroos groenroos self-assigned this Dec 30, 2020
@groenroos groenroos added the low priority Issues which should only be considered after everything else is done label Aug 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@groenroos groenroos

Labels
enhancement Improvements to existing features and functionality low priority Issues which should only be considered after everything else is done refactoring Drastic code quality improvements
Milestone
M3 - Release 3.0
Development

No branches or pull requests
1 participant
@groenroos