Add raw values endpoint for localizations - #5
Open
StudioSomniaBV wants to merge 2 commits into
Open
Conversation
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
1 participant
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.
Adds GET .../localizations/{site}/values for entries and terms. It returns the publish-form values in the raw stored format (same data the CP edit screen uses), plus localizedFields, hasOrigin, originValues and optionally the blueprint (?with_blueprint=1).
Reason: the show endpoint returns augmented values — bard fields come back as HTML strings, which cannot be written back through blueprint processing. A PATCH with such a value returns 200 but silently persists nothing for that field. With this endpoint clients can round-trip structured fields: read raw values, change only text nodes, PATCH back.
Reuses the exact CP edit call the update methods already make internally; no new mechanics.