flow-generator

Flow generator

Read an Adapty flow's builder config, transform it, check the result, and write it back. Transforming a config that exists is the default, and the safer path: everything you emit is then grounded in a document that already works.

Authoring a new flow is also in scope, and two things — and only these two — genuinely cannot be synthesized:

• An image you have no readable FILE for. Given a path you can now upload it — flows media upload (media.md). An image you can only see — pasted or attached into the conversation — is not one you have: ask for a path. With no file there is nothing to upload, so its catalog entry stays empty, never a made-up URL (trap 5). SVG uploads fail, so a monochrome glyph is authored inline in _meta.icons; a graphic no element can express, you draw and rasterize (media.md). An icon is not in this list: python3 references/icons.py --search <word> resolves any phosphor glyph, and an invented name draws blank however good your markup is (trap 23).
• Real store prices. They come from the store, not from Adapty; products create has no price flag.

Everything else is reachable: product UUIDs from adapty products list (or products create), theme colours sampled off a reference screenshot, and icon markup resolved from the bundle references/icons.py ships.

flowProductId — the per-screen declaration in _meta.screens[].products[] — is derived, not waited for. flowkit.predeclare(screen_id, products) writes the block; pass exact Product + Offer pairs, a bare product id or a (product_id, offer_id) tuple, because the offer is part of the id. Omit the declaration and device preview 422s. When rewriting a flow, carry the live _meta.screens forward instead of regenerating it — and screens[].products with it, the screen-owned registry that _meta is derived from. Never write "products": []: absent and empty mean opposite things to the builder. When authoring, flowkit.screen() writes the registry and the structured product refs for you, from the screen's own bindings — bind an offer with product(..., offer_id=...) and a dotted price variable picks it up (products.md). When you do author, references/flowkit.py owns the mechanical parts — the hierarchy/map split above all — and patterns.md owns the shapes.

It also covers conditions (when/ref/all_/not_empty), all fourteen action types, the eight inputs and the tabs composite — each raising on the shape the transform service refuses.