point the state and feature moderation call sites at the sdk

Query, notification and feature-level moderation reads switch to the sdk types
and take their `moderate*`/`hasMutedWord` entry points from the
`lib/moderation/subjects` seam, since these paths still carry
`@atproto/api`-typed views.

`shouldFilterNotif` is the one behavioral seam worth noting: its notification
and facet values come from an unmigrated read, so the mute-word check goes
through the widening wrapper rather than the sdk export directly.
This commit is contained in:
Samuel Newman
2026-08-04 02:36:02 +03:00
parent f1411df0a4
commit de09c83f99
17 changed files with 30 additions and 40 deletions
+1 -1
View File
@@ -4,7 +4,6 @@ import {
type AppBskyFeedDefs,
type AppBskyGraphDefs,
AtUri,
moderateFeedGenerator,
} from '@atproto/api'
import {type AtUriString} from '@atproto/syntax'
import {RichText} from '@bsky.app/sdk/richtext'
@@ -20,6 +19,7 @@ import {
} from '@tanstack/react-query'
import {DISCOVER_FEED_URI, DISCOVER_SAVED_FEED} from '#/lib/constants'
import {moderateFeedGenerator} from '#/lib/moderation/subjects'
import {sanitizeDisplayName} from '#/lib/strings/display-names'
import {sanitizeHandle} from '#/lib/strings/handles'
import {asSdkFacets} from '#/lib/strings/rich-text-helpers'