Update client-server API endpoints to move from r0 to v3 (plus whitespace fixes) #3421
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
turt2live
added this to Needs idea feedback / initial review
in Spec Core Team Backlog
via automation
turt2live
moved this from Needs idea feedback / initial review
to Requires spec review (post-FCP)
in Spec Core Team Backlog
erikjohnston
approved these changes
Oct 12, 2021
turt2live
moved this from Requires spec review (post-FCP)
to Done to some definition
in Spec Core Team Backlog
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.
As per MSC2844
This spec PR covers the actual
r0 -> v3transition as well as some whitespace fixes in affected files (sorry, these were automatically applied by my IDE).This is reviewable commit-by-commit if you'd like to take a look at the stepped approach.