Version: 0.33.0.
The content list badges rows with "Pending changes" (draft revision differs from live), but the status filter can only express Published/Draft/Scheduled/Archived — there is no way to surface all published entries with unpublished edits at once, which is the review queue an editor actually wants before a publish pass.
Suggestion: a "Pending changes" option in the status filter (server-side: live_revision_id IS NOT NULL AND draft_revision_id IS NOT NULL AND draft_revision_id != live_revision_id, i.e. the same condition as getDraftStatus() === "published_with_changes"), or a sortable pending-changes column. The list query schema already types status as an open string, so a virtual status token slots in cleanly — we're running exactly that as a local patch (repo + list FilterBar) and happy to PR it.
Version: 0.33.0.
The content list badges rows with "Pending changes" (draft revision differs from live), but the status filter can only express Published/Draft/Scheduled/Archived — there is no way to surface all published entries with unpublished edits at once, which is the review queue an editor actually wants before a publish pass.
Suggestion: a "Pending changes" option in the status filter (server-side:
live_revision_id IS NOT NULL AND draft_revision_id IS NOT NULL AND draft_revision_id != live_revision_id, i.e. the same condition asgetDraftStatus() === "published_with_changes"), or a sortable pending-changes column. The list query schema already typesstatusas an open string, so a virtual status token slots in cleanly — we're running exactly that as a local patch (repo + list FilterBar) and happy to PR it.