Support exposing contract error reason and not just code and a generic message

[yoga-braavos]

Current spec mandates a hardcoded error message on contract errors. This prevents clients from programmatically proess such errors:

starknet-specs/api/starknet_api_openrpc.json

Line 3597 in cddef47

"CONTRACT_ERROR": {

We need to add to the spec the actual contract error so that clients will have programmatic access to this info

[Cevedale]

You can try updating the API Specification:
Open the starknet_api_openrpc.json file at line 3597 and add the necessary details for the contract error. You should update the "CONTRACT_ERROR" section to include fields that provide programmatic access to the error information.

For example:

json
Copy code
"CONTRACT_ERROR": {
"type": "object",
"properties": {
"code": {
"type": "integer",
"description": "Error code for the contract error."
},
"message": {
"type": "string",
"description": "Error message for the contract error."
},
// Add other relevant fields as needed
},
"description": "Details of a contract error."
},
Make sure to customize this based on the specific information you want to provide for contract errors.