Skip to content

flow-schema-extraction entrypoint drops schemas of inline sub-flows - #190

Merged
nicosammito merged 2 commits into
mainfrom
feat/#189
Nov 6, 2026
Merged

nicosammito merged 2 commits into
mainfrom
feat/#189

Conversation

@nicosammito

Copy link
Copy Markdown
Member

Close #189

InlineReferenceValue carries an optional database_id as of this version
(code0-tech/tucana#377), which the schema extraction needs to address an
individual inline reference.
getFlowSchemas enriches sub-flows sitting as an InlineReferenceValue inside
a literal's references since #188, but flow-schema-extraction only reported
parameters whose value is a SubFlowValue, so those schemas were discarded
before serialization.

The entrypoint now descends into a literal parameter's references, nested
literals included, and reports every sub-flow it finds under a new
subflowReferences key, addressed by the id of the inline reference holding
it. The mapper maps that id from the proto's database_id.

Since database_id is optional, a reference without one is left out rather
than reported with a null id, which would make the consumer match the
wrong rows.

Closes #189
@nicosammito nicosammito self-assigned this Nov 6, 2026
@nicosammito
nicosammito merged commit e81a62b into main Nov 6, 2026
3 checks passed
@nicosammito
nicosammito deleted the feat/#189 branch November 6, 2026 23:39
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.

flow-schema-extraction entrypoint drops schemas of inline sub-flows

1 participant