Headless CMS / createRevisionFrom - Ensure Published Records Are Updated Accordingly
#4180
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
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.
Changes
Prior to this PR, if a user would be using the
createRevisionFrommethod (directly or via GraphQL API), and also set the initial status of the revision topublished, then, subsequently trying to read the entry via the READ GraphQL API would still return the old published version.This was happening because, upon creating+publishing the new entry revision, the storage operations code would not take the
statusinto account, and do required updates on the "published" record for the CMS entry in question.With this PR, this issue has been fixed.
How Has This Been Tested?
Jest.
Documentation
Changelog.