-
Notifications
You must be signed in to change notification settings - Fork 618
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
re: Rename active peer to connected peer terminology in near-network
#5428
re: Rename active peer to connected peer terminology in near-network
#5428
Conversation
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.
I am approving to unblock the PR, but it is important to address the backward compatibility comment
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.
let's make sure that backwards compatibility is fixed before proceeding with this PR
We should remove `serde` from `near-client-primitives`. It's only needed by `jsonrpc`. More changes will be required, to separate `jsonrpc` api, from rest of the code base, but that's a first step. See #5516 Blocks #5428 (review)
e12c9df
to
4c25088
Compare
608e299
to
4c25088
Compare
4c25088
to
5af01ea
Compare
Minified changelog: - `near-account-id` has gained significant QOL and design improvements. #5575 #5581 #5660 - `near-client-primitives` was detached from the public jsonrpc API. `NetworkInfoResponse` is now directly flattened into `RpcNetworkInfoResponse`. #5428 #5515 And much more.. crates-0.10.0...crates-0.11.0
Change terminology used in
near-network
to be more accurate.Currently we use
active peer
terminology to meanconnected peer
.Unfortunately, that term is not self explanatory and leads to some confussion.
See #5424
Blocked by #5515