feat(home): add Recently Responded sort and i18n the Pending filter#1526
Open
lol2x wants to merge 1 commit into
Open
feat(home): add Recently Responded sort and i18n the Pending filter#1526lol2x wants to merge 1 commit into
lol2x wants to merge 1 commit into
Conversation
Adds a new sort option that orders posts by when an admin last responded (changed status). The view filters out posts with no response_date so the sort is meaningful regardless of the active status filter — i.e. selecting "Recently Responded" while the default Open/Started/Planned filter is on shows only posts that have actually been acted on, instead of a long tail of unresponded posts in arbitrary order. Also wires the Pending status filter (visible to collaborators/admins) and the inline "pending" badge in ListPosts through i18n; both were previously hardcoded English. Adds Polish translations for the new and existing keys. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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.
Summary
response_date(when an admin last changed status), newest first.response_date IS NULLso the sort stays meaningful regardless of the active status filter. Without this, picking the new sort while the default Open/Started/Planned filter is active produces a long tail of unresponded posts in arbitrary order.ListPosts— both were previously hardcoded English.Why
Admins/collaborators often want to review what's been recently dealt with — completions, declines, planned items — without having to also remember to flip the sort manually. Sorting by
id/creation date doesn't surface this; the existing per-statusplanned/completed/declinedviews are deprecated in favor of status filters but those don't carry the response-date sort. This stitches that gap.Behavior
response_dateis preserved).