Reduce all worker exceptions to common #1249
Comments
There are 2 ways to make common exceptions:
error: incorrect_techspec_state error: incorrect_techspec_state error: incorrect_techspec_state
error: incorrect_techspec_state error: incorrect_techspec_state error: incorrect_techspec_state |
Same way should be used to declare Also, another logic exceptions can be just replaced with single logic exception without custom fields. |
It should be 2 exceptions - Techspec is already finished and Techspec is not yet approved. Message for client should be informative. Client should just translate it to user language and show to user. |
…evel Refactor worker exceptions #1249
PR #1321 |
Currently there are too many different worker logic exception types (>30).
But most of evaluators are throwing 2 or 3 exceptions only.
If client is a software, the common error description is enough.
E.g.:
incorrect_techspec_state
.If client is a human (e.g. user of cli_wallet, or programmer who plays with API), he can read the message of the exception. Single exception can be used with few messages. Also, it anyway should be described in documentation: which operation for which techspec state.
The text was updated successfully, but these errors were encountered: