You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Saves collection ordering changes as drafts, when enabled. Queries for published docs now retain the previous order until the moved document is published, more closely aligning with expected behavior.
Use case: image you have a front-end website that renders a list of documents, queried by order. You might not want reorders to be made live until you explicitly publish them.
Collections without drafts and orderable joins retain their existing behavior.
I personally think this may confuse clients, if they reorder a few documents, they now have to track which documents they have moved to remember to publish. If they have changes in a few other documents too, going by "draft" alone isn't enough. It creates a visual distinction between how the list is ordered and how it's ordered on the frontend. This would then be something we have to explain.
Maybe orderable needs to become a true for defaults, or an object:
orderable: {
publishOnReorder: true
}
for example.
EDIT:
We had a client with a document at 101 which they wanted to move, because of pagination being 5, 10, 25, 50 and 100 - they couldn't move it. Dragging is a good UX for small list, but for a larger list I think something like this would be better:
payload-move.mp4
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
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.
Saves collection ordering changes as drafts, when enabled. Queries for published docs now retain the previous order until the moved document is published, more closely aligning with expected behavior.
Use case: image you have a front-end website that renders a list of documents, queried by order. You might not want reorders to be made live until you explicitly publish them.
Collections without drafts and orderable joins retain their existing behavior.
Before
payload-e2e-before.mp4
After
payload-e2e-after.mp4