Typeahead search (POST graphql/query, TypeaheadSearchQuery): the streaming
results the app shows as the user types. The response is GraphQL incremental
delivery — a @defer/@stream payload followed by patches, one of which is a
batched JSON array of patches — so the body is split and merged
(parseJson) before decoding into the typed result union.
The app fires two TypeaheadSearchQuery requests for one settled text when
its configuration says so — a keyword-only one (KEYWORD,
OVERFETCHED_KEYWORDS) and the full one, sharing the typing session and its
rank token — and the full one alone otherwise. Whether the companion goes
out, and the three skip_over_fetched_* variables both requests carry, are
the account's configuration (TypeaheadRequestShape, derived by the platform layer:
the Android 451 recordings hold the companion with the flags false on the
follow scenes' account, with the flags true on the Direct scenes' account,
and no companion with the flags true on the account of the nine older
scenes). The response decoded here is the full request's, the stream the
field shows. The two go out together (the keyword-only request first, the full
one right after it): the full request does not wait for the companion's
answer, and a companion that fails does not stop it.
Does not navigate; the screen that hosts the search field emits the
navigation.
Typeahead search (
POST graphql/query,TypeaheadSearchQuery): the streaming results the app shows as the user types. The response is GraphQL incremental delivery — a@defer/@streampayload followed by patches, one of which is a batched JSON array of patches — so the body is split and merged (parseJson) before decoding into the typed result union.The app fires two
TypeaheadSearchQueryrequests for one settled text when its configuration says so — a keyword-only one (KEYWORD,OVERFETCHED_KEYWORDS) and the full one, sharing the typing session and its rank token — and the full one alone otherwise. Whether the companion goes out, and the threeskip_over_fetched_*variables both requests carry, are the account's configuration (TypeaheadRequestShape, derived by the platform layer: the Android 451 recordings hold the companion with the flagsfalseon the follow scenes' account, with the flagstrueon the Direct scenes' account, and no companion with the flagstrueon the account of the nine older scenes). The response decoded here is the full request's, the stream the field shows. The two go out together (the keyword-only request first, the full one right after it): the full request does not wait for the companion's answer, and a companion that fails does not stop it.Does not navigate; the screen that hosts the search field emits the navigation.