-
Notifications
You must be signed in to change notification settings - Fork 224
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: remove remaining directory server mentions #3048
RPC: remove remaining directory server mentions #3048
Conversation
26e4cf0
to
352b687
Compare
@dtinth I'd also appreciate your review, but I can't add you as a reviewer for some reason. |
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.
Btw, this is a breaking change for consumers, but since JSON-RPC is “experimental” it does not need to obey semver. Still, it may be worth mentioning in the changelog to make this change less surprising.
Yeah, true. Done. |
I think everything is documented here too? @pljones please drop needs documentation if you think it's valid to drop. |
Mmm, the doc-gen stuff is there. We don't do jamuluswebsite doc for JSONRPC, right? |
True. There's not much on the website. The actual documentation of the API is currently in the repo. |
Unlabelled, then. |
Short description of changes
CHANGELOG: RPC: Rename
directoryServer
todirectory
injamulusserver/getServerProfile
responseContext: Fixes an issue?
RPC changes separated from main change due to RPC doc issues that got resolved.
Does this change need documentation? What needs to be documented and how?
RPC doc changes in line with API change.
Status of this Pull Request
Untested as I don't use RPC.
What is missing until this pull request can be merged?
Seems trivial, so I'd just do it. I've been running builds with this change in (but without using the RPC API).
Checklist