Tags: getfider/fider
Tags
fix(post-filter): harden post filter against edge cases
* refactor(sqlstore): parameterize tag placeholder in getViewData
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(search): respect status, tag, and ownership filters when query is set
Previously, providing a search query bypassed the user's active filters and
returned posts across all five statuses with no tag/votes/ownership filtering.
The search branch now uses getViewData() like the no-query branch, so filters
behave consistently with or without a search query. Sort during search remains
score-based (ts_rank_cd).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(home): keep filter sidebar visible while searching
The PostFilter component is now rendered regardless of whether a search query
is active, so users can see and change filters during search. PostsSort stays
hidden during search because results are ranked by full-text score.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(home): expand search input width when filter remains visible
With the filter sidebar now visible during search, the existing
4-column 1fr grid still reserved 25% width for the filter column —
leaving a large empty gap between the small filter button and the
narrow search input. Switch to an `auto 1fr` grid template when
searching so the filter column shrinks to the button's width and
the search input fills the remaining horizontal space on md+.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(search): cover filter combinations with active query
Add TestSearchPosts_RespectsFilters with table-driven cases verifying
that a search query honors status, tag, MyVotes, MyPosts, and NoTags
filters, and that the default status set excludes Completed and
Declined posts.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(search): guard MyPostsOnly against nil user
An unauthenticated request with myposts=true previously panicked on
user.ID. The frontend hides the option from anonymous visitors, but
the API parameter was still accepted, so direct calls crashed the
handler. Silently ignore the flag when there is no authenticated user.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(search): NoTagsOnly takes precedence over Tags
When both filters were set on the same request (possible via direct API
call or stale URL params), the SQL combined "AND tags = '{}'" with
"AND tags && \$N" — always false — silently returning zero rows. Make
NoTagsOnly authoritative: when set, tag filters are dropped from both
the SQL condition and the parameter list.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(home): make Untagged and tag filters mutually exclusive
Selecting Untagged while specific tags are active (or vice versa) put the
filter UI in a contradictory state that returned zero results. Toggling
on either kind of filter now clears the other.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Add `tenant.AllowedSchemes` advanced configuration item (#1332) * Add tenant.AllowedSchemes advanced configuration item Specifying ^monero:[48] or ^bitcoin:(1|3|bc1) allows cryptocurrency payment links These were rendered but then sanitised away to <a>...</a> w/o href= Ref: https://bounties.monero.social/posts/15/1-200m-monero-bounties-site-parse-donation-address-as-link * Ship the config via useFider() * Work around useContext() restrixion in test * Disable allowed schemes by setting ALLOW_ALLOWED_SCHEMES=false * Hide Allowed URL Schemes config if disabled * Bump migration date
PreviousNext