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
src/features/admin/attendees-list.ts:56:52 ?? → || # parsePositiveInt validates against PositiveIntSchema (minValue 1), so it returns a number of 1 or more, or null — it can never return 0, the only falsy number that would tell ?? and || apart
992
993
src/features/admin/listing-page-data.ts:282:61 ?? → || # Map.get returns ListingWithCount[] | undefined, and every array — empty included — is truthy, so only undefined reaches the fallback and both operators yield the same []
993
994
995
+
# The news card query names a single table, so its columns need no alias to
996
+
# resolve.
997
+
src/shared/db/news-posts.ts:148:47 news_post → "" # dropping the alias leaves the column names unqualified, and the read selects from one table (news_posts AS news_post) plus scalar subqueries that carry their own qualified id, so every name still resolves to the same column
998
+
994
999
# A revision a row rule already makes unreachable.
995
1000
src/shared/db/migrations/schema/payments/cases.ts:42:70 1 → 0 # alert_sent_revision can never be 0 while it is there: the row rule "alert_sent_revision IS NULL OR (alerted_revision IS NOT NULL AND alert_sent_revision = alerted_revision)" ties it to alerted_revision, whose own floor is 1, so the value is either missing (both floors pass) or at least 1
0 commit comments