Variable ProfileGridEntrySchemaConst
ProfileGridEntrySchema: Struct<
{
authorId: optionalKey<String>;
carousel: optionalKey<
Struct<{ children: $Array<String>; size: optionalKey<Number> }>,
>;
dashManifest: optionalKey<String>;
mediaId: String;
mediaType: optionalKey<Number>;
position: Number;
takenAt: optionalKey<Number>;
trackingToken: optionalKey<String>;
videoDuration: optionalKey<Number>;
},
> = ...
One tile of the profile's media grid: the media and its position in the grid. The telemetry facts the posts feed's video view reports are the media answer's: its author, when it was taken, its organic tracking token, a video's duration and its DASH manifest. What the tile opens into needs more — the whole grid page (the posts feed's first page is answered by the grid's own answer: the app sends no request on the tap,
ContextualFeedFragment), the profile the grid belongs to, the viewer's relationship to it and the answer's continuation — and those are the profile screen's state, which the tile reads as its host's (ProfileGridHostStateSchema); the entry carries none of them.