Conversation
github-actions
Bot
added
the
documentation
Contributor
|
in the not too distant future we'll be "present V2 API before V1 api" ;-). THis is great. |
Contributor
|
Let's merge this! Also, I didn't remember that you had opened this, so I did this same thing, but much deeper when I tackled the "v2 /update" pr work when I took up your suggestion to have just one page instead of two for v1 and v2... |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The "Indexing with Update Handlers" page presents XML first, then JSON, then CSV. JSON is by far the most common format for update requests these days, so it should come first.
This is a pure section move: the JSON chapter is moved above the XML chapter, and the two intro sentences that list the formats are re-ordered to match. No content changes.