feat: discard drafts when enabling draft and publish on ct #20257
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.
What does it do?
On V5, content types without draft and publish have a single version , where the publishedAt value is filled with a date.
Content Types with draft and publish have two versions, a draft and a published version, where the publishedAt value is null on drafts and filled with a date on published versions.
When enabling draft and publish on a content type, we were copying the single version with the publishedAt value filled and updating the publishedAt value to be null.
This process did not copy components or relations, and now all documents are processed in batch, to call the
documents.discard
method, which takes care of that, at the cost of processing one version at a time.