Skip to content

docs(cli): document the fonts commands and the font refresh of flows publish - #885

Open
teozee-adapty wants to merge 6 commits into
mainfrom
feat/flow-fonts
Open

teozee-adapty wants to merge 6 commits into
mainfrom
feat/flow-fonts

Conversation

@teozee-adapty

Copy link
Copy Markdown

What

Document the new adapty fonts commands and the font refresh of flows publish.

  • developer-cli-flows: a "Custom fonts" overview (the app must bundle the same fonts; how a config names a font), one section per fonts command (upload results, collisions with --choice, exit codes), and the font refresh under flows publish.
  • developer-cli-reference: the Flows row names fonts.
  • flow-generator-skill: "Custom fonts stay manual" becomes "Give it your fonts".
  • reuse-flow-elements, using-custom-fonts-in-flow-builder, migration-from-revenuecat: the claims that fonts are builder-only are corrected; a new "Upload fonts from the terminal" section.

Checks

MDX lint and parse, internal links, unit tests, the English build and the external link check pass.

Draft until the CLI change is ready.

…publish

Custom fonts are no longer builder-only: the CLI uploads and manages them,
and the flow-generator skill uses those commands. The CLI flows page gets the
fonts commands, the upload and collision rules, the exit codes and the bundle
reminder; flows publish says it refreshes the fonts copy first. The skill,
custom fonts, reuse and RevenueCat migration pages drop the builder-only claims.
…and add the direct API publish steps

A text style keeps family and weight in its settings, an element in
props.font; the nearest face prefers the same style and the lighter face on
a tie. A weight collision is within the family, an iOS name collision is
app-wide, and choices come only with a refusal that offers them. The upload
table gets exit 2 for an unreadable file and splits exit 3. A Developer API
caller gets the font refresh steps before a publish. The skill and reuse
pages use a suitable existing family and link the video upload.
…place and the publish font stops

A colliding font file is refused with every colliding face, and
--choice replace puts it on all of them. The variable file results are
told apart. fonts faces replace asks first and needs --yes without a
terminal (exit 6). flows publish stops before any write on a font name
several families share or a config answer without updated_at. A stopped
package gives flows_to_publish null with a recovery step, and fonts usage
lists only flows that name the family by id. The direct API steps name
expected_updated_at and give the full _meta.fonts mapping, keeping a
bundled font entry.
…ing when it runs, and cover uncertain uploads and the publish lock

--choice replace reads the collisions again and replaces every face that
collides when it runs, so the pages say to check the list right before and
to read replaced_faces after. A variable font file is refused only when all
its styles are taken or a new style has an iOS name another face has. A
failed file may be stored, the last one too: fonts list before a resend.
flows publish needs updated_at and remote_configs only when the font copy
needs a save.
… file, and cover the app-wide iOS name and the unread flows answer

The run without a choice before a replace can upload the file when the
collision is gone; the page then stops there instead of following with
--choice replace, which could replace the new face. The fonts add choice
says a face of another family collides on its iOS font name, and exit 4
covers a stored package whose flows answer could not be read.
@teozee-adapty
teozee-adapty marked this pull request as ready for review November 21, 2026 09:40

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant