Semantic error messages #8646
Labels
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
type:refactor
Refactoring or improving of existing code
I'd like for our error handling to be more robust and thinking of ways in which we can control:
One possibility would be that instead of throwing
new Error(X)
we could have classes of errors e.g. mapped to the above. Something like this could mean we have less string-checking of error messages in our error handling and instead can know whether to pass it up or log and consume it.Another thing I need from the app perspective is to know which repo-level errors are "permanent" - e.g. disabled by config, a fork, etc.
The text was updated successfully, but these errors were encountered: