Variable MediaCommentsInputSchemaConst
MediaCommentsInputSchema: Union<
readonly [
Struct<
{
carouselIndex: optionalKey<Union<readonly [Number, String]>>;
commentSessionId: optionalKey<String>;
feedPosition: optionalKey<Union<readonly [Number, String]>>;
mediaId: String;
surface: Literal<"feed">;
},
>,
Struct<
{
chainingPosition: optionalKey<Union<readonly [Number, String]>>;
chainingSeedMediaId: optionalKey<String>;
chainingSessionId: optionalKey<String>;
clientPosition: optionalKey<Union<readonly [Number, String]>>;
commentSessionId: optionalKey<String>;
mediaId: String;
rankingSessionId: optionalKey<String>;
storyRankingToken: optionalKey<String>;
surface: Literal<"reels">;
},
>,
],
> = ...
What the comments sheet is opened with: one of two variants, told apart by the surface it sits over. The variant decides both wire variants of the comment body (and the module the navigation renders); an illegal mix of the surfaces' fields is not representable. The notes the composer shows are not an edge argument: the server issued their ids to this process (
repost), so the sheet reads them from its own state on enter, as the ids this process created — a proxy for the composer's full set, whichstream_commentswould carry and the library does not model.