-
Notifications
You must be signed in to change notification settings - Fork 11.4k
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
[RPC] - Gateway should deserialize object contents #1313
Comments
@oxade FYI |
Are we keeping the rest server endpoints for devnet? I thought we were dropping the rest endpoints and going with json-rpc over https? i.e. are we going to be able to hit /api/object_info with a REST verb? |
This endpoint will be port to JSON-RPC, instead of /api/object_info, the same functionality will be accessible via json RPC. We will remove the rest server after JSON-RPC is ready. |
Ok, so we will never do this? Should we close the issue? |
This isn't specific to REST api - it's about returning object contents in a readable format to clients. |
Lets keep this open to make sure we fix this in RPC |
Related to this #237 |
this is fixed by #1440 |
Currently the rest server outputs raw
ObjectRead
data for /api/object_info, as in:Ideally it should serialize to something readable, like json, similar to what the wallet CLI already does.
The text was updated successfully, but these errors were encountered: