Reposts a feed media via a note: reads the media info (for the tracking token,
the container id and the carousel child), optionally likes the media (only
when like: true), then creates the repost note attached to the carousel
child (or the container). How the text reaches the note is the application
profile's fact (MobileApplicationState.mediaRepostWire): an 'editor'
build creates a blank note and, when a non-empty text is provided, sets it
through UpdateMediaNoteRepostTextRequest; a 'note-with-text' build sends
the text in the note itself and never sends the update. A profile that declares
neither is no evidence of a way, so the brick fails with
MobileMediaRepostWireNotDeclaredError. The created note is recorded in the
process's note registry (MediaRepostNotes), so a comments sheet opened
over the same media sees the note the app showed, exactly as after the post
screen's repost.
Every value is chained from the media info response, the navigation's wire
values (NavigationWire: chain and container module), or the caller's feed
context — nothing is copied from a capture. Emit
NavigateTo(MobileScreens.PostOpenedFromLink, 'button') before the call so the
container module and the rendered chain name the short-url feed.
Reposts a feed media via a note: reads the media info (for the tracking token, the container id and the carousel child), optionally likes the media (only when
like: true), then creates the repost note attached to the carousel child (or the container). How the text reaches the note is the application profile's fact (MobileApplicationState.mediaRepostWire): an'editor'build creates a blank note and, when a non-emptytextis provided, sets it throughUpdateMediaNoteRepostTextRequest; a'note-with-text'build sends the text in the note itself and never sends the update. A profile that declares neither is no evidence of a way, so the brick fails withMobileMediaRepostWireNotDeclaredError. The created note is recorded in the process's note registry (MediaRepostNotes), so a comments sheet opened over the same media sees the note the app showed, exactly as after the post screen's repost.Every value is chained from the media info response, the navigation's wire values (
NavigationWire: chain and container module), or the caller's feed context — nothing is copied from a capture. EmitNavigateTo(MobileScreens.PostOpenedFromLink, 'button')before the call so the container module and the rendered chain name the short-url feed.