You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to send some details about the error to the client, I found out that the "error" field in response is automatically casted to string ( see. connection.js:104 ), although the "error" field in JSON RPC 2.0 should be an object (see http://www.jsonrpc.org/specification#error_object ) with "message", "code" and "data" subfields.
The text was updated successfully, but these errors were encountered:
indeed @phrenciuc, the canonical errors (and error codes) were introduced in a patch but they wasn't implemented (although they ARE passed to the error handler), but the code and the data fields are indeed dropped
First of all congrats for this great extension!
Trying to send some details about the error to the client, I found out that the "error" field in response is automatically casted to string ( see. connection.js:104 ), although the "error" field in JSON RPC 2.0 should be an object (see http://www.jsonrpc.org/specification#error_object ) with "message", "code" and "data" subfields.
The text was updated successfully, but these errors were encountered: