diff options
| author | erdgeist <erdgeist@erdgeist.org> | 2026-07-12 14:26:30 +0200 |
|---|---|---|
| committer | erdgeist <erdgeist@erdgeist.org> | 2026-07-12 14:26:30 +0200 |
| commit | 5803c59192b7fb05840d0b452eb64d9f997f3d8f (patch) | |
| tree | 09ce87657484ce8508dd6fca12570c0d044f3819 /public/stylesheets/ie.css | |
| parent | 19e0ee821d5b2b6d3397a81411f4f3a4cbd2fa83 (diff) | |
Extract drafts/recent query logic from controller into Nodeerdgeist-revive-events
Node.drafts_and_autosaves and Node.recently_changed replace inline
query logic in NodesController#drafts/#recent -- pure refactor, no
behavior change for either action. The real reason: the dashboard's
upcoming abridged widgets need the exact same queries the full pages
already use, just limited and (for drafts) sorted with the current
user's own locked nodes first. Better to share one method than let a
widget and a full page quietly drift onto two versions of "what counts
as a current draft."
current_user_id: is an explicit, optional argument rather than a
separate method -- ordering by lock ownership only applies when a user
is given; omitted entirely, it's pure recency, exactly today's
behavior. Needed Arel.sql wrapping a sanitized CASE expression before
.order would accept it -- sanitize_sql_array only vouches for the
values inside the string, a separate Rails safety check still refuses
any string shaped like more than a plain column reference unless it's
explicitly marked as already-vetted.
Diffstat (limited to 'public/stylesheets/ie.css')
0 files changed, 0 insertions, 0 deletions
