-
Notifications
You must be signed in to change notification settings - Fork 11
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
How are bad input parameters handled? #84
Comments
Each RPC call is an independent entity. The input parameters are checked, and RPC errors returned on bad values. Error codes are not unique at this stage, but the human readable errors describe the error. It is on the 'todo' list to go through every human readable error and assign unique error codes etc to these but not prioritized highly, as we're often moved onto new things as soon as something 'works' rather than 'finished'. Thanks |
Example
|
Got it. Thx. |
Slightly related: I think getXbalance should not throw exceptions, but rather respond with 0.0 or an empty array, if "address does not exist (for property N)", unless input format is wrong. |
What does MasterCore do & return when an invalid value is passed as an input parameter, e.g. to one of the query api's? Is that detected as an error or does it just return nothing?
Is there a list of error codes and their meaning?
The text was updated successfully, but these errors were encountered: