fix: Return experimental endpoint for light_client_proof RPC
#2874
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
bowenwang1996
approved these changes
Jun 19, 2020
|
@evgenykuzyakov I agree that would be the proper way to do it, unfortunately we haven't done it for |
frol
approved these changes
Jun 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Otherwise the current nearlib tests are failing, because they still depend on the
EXPERIMENTAL_light_client_proof.The proper migration should be first introducing
light_client_proofthen moving nearlib API to the new RPC endpoint. And once all chains are upgraded to the new endpoint, only then the EXPERIMENTAL endpoint can be deprecated.Test plan: