feat(flows): add flow + builder config commands - #13
Open
mlnchk wants to merge 5 commits into
Open
Conversation
mlnchk
force-pushed
the
prepare-cli-support-mr-13309
branch
from
August 18, 2026 13:20
6a6f68e to
6d1b462
Compare
Add Developer API flow support: flows list/get/create and flows config get/update (builder config with optimistic lock).
mlnchk
force-pushed
the
prepare-cli-support-mr-13309
branch
from
August 18, 2026 13:39
72610c2 to
a0302b4
Compare
ApiError.message was set to the error code (e.g. 'validation_error'), so oclif printed cryptic errors like 'ApiError: validation_error'. Compose the message from the server's field errors (falling back to the code) and expose it as oclif's `code`, so every command surfaces the real reason (e.g. 'Flow version does not exist.').
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds CLI support for the five new Developer API flow endpoints, following the existing paywall/placement proxy pattern.
Commands
flows list --app UUIDGET .../flows/(paginated)flows create --app UUID --namePOST .../flows/flows get --app UUID FLOW_IDGET .../flows/<id>/flows config get --app UUID FLOW_IDGET .../flows/<id>/config/flows config update --app UUID FLOW_IDPUT .../flows/<id>/config/Notes
config updatetakes the builder config via--config(inline JSON) or--config-file PATH/-(file/stdin), reusing the repo's existing file-read pattern. Config is forwarded verbatim —FlowFrontConfigis the schema of record downstream.--remote-configs(JSON array) and--expected-updated-at(optimistic-lock token) map to the write DTO.config update;config getreturns 404 until then.FlowStatustyped asstring— the server enum's full value set isn't in the MR diff, so narrowing was avoided.Supporting changes
src/lib/api-schemas.ts— flow DTOs.package.json—flowsandflows:configtopics.README.md+CLAUDE.md— docs.test/commands/flows.test.ts— 6 tests covering all routes and body/lock-token forwarding.Verification
pnpm buildclean,pnpm test(mocha + eslint) → 140 passing.