-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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 Server] Simplify the response schema for object_info #1440
Conversation
Unfortunately this will break Lines 191 to 195 in 72dbf0b
The plan was to simplifying the model once the JSON-RPC work is in, we will need to make this changes in sui/sui_core/src/gateway_state.rs Line 176 in 72dbf0b
instead of changing the model in the Rest layer, or else the RestGatewayClient implementation won't be able to talk to the rest server.
Also isn't the plan to move to JSON-RPC and remove the Rest server all together? The rest server will be removed soon.... |
@patrickkuo thanks for flagging this! The reason I was working on this PR is because I was working on the TypeScript SDK and found
This sounds great! I'll then base this PR against
I thought the conclusion is to keep the REST server code and revisit the decision sometime later. However, I am totally okay with remove the REST server code for now if it slows us down. The primary change in this PR is the conversion from |
b540d25
to
74f8cdd
Compare
This PR will fix part of this issue #237 |
74f8cdd
to
a83e0a7
Compare
0baf028
to
a1e1cc9
Compare
@patrickkuo , there're two ways for fixing the issue you mentioned
I ended up implementing Option 2 for the following reasons:
Let me know if you have any concern. |
Sounds good to me, let's have this endpoint to unblock others, I will investigate if it make sense to implement option 1 after this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
a1e1cc9
to
1f91097
Compare
The response returned by the existing
object_info
is too complicated for the client applicationsBefore
After
There are still plenty of room for improvement(e.g., simplify the
contents
field), but that's for a separate PR