Skip to content
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

Namespace all routes inside of RPCClient #3769

Merged
merged 1 commit into from
Apr 10, 2023
Merged

Conversation

NullSoldier
Copy link
Contributor

@NullSoldier NullSoldier commented Apr 10, 2023

Summary

This should make the client a bit nicer to use, because you can just look at each object there and find all the chain apis under chain. You also can now just name things in a lot simpler ways. We should start renaming routes to remove the namespace from the route if its duplicated.

// Before
client.getNodeStatus()
// After
client.node.getStatus()

Testing Plan

It only changes the client which should get caught in builds.

Documentation

Does this change require any updates to the Iron Fish Docs (ex. the RPC API
Reference
)? If yes, link a
related documentation pull request for the website.

[ ] Yes

Breaking Change

Is this a breaking change? If yes, add notes below on why this is breaking and
what additional work is required, if any.

[x] Yes

Need to add a note about this in the release notes.

@NullSoldier NullSoldier requested a review from a team as a code owner April 10, 2023 18:19
this should make the client a bit nicer to use, because you can just
look at each object there and find all the chain apis under chain. You
also can now just name things in a lot simpler ways. We should start
renaming routes to remove the namespace from the route if its
duplicated.
@rohanjadvani rohanjadvani merged commit a6297cd into staging Apr 10, 2023
@rohanjadvani rohanjadvani deleted the jason/rpcclient branch April 10, 2023 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants