Skip to content

fix NamedTupleParser::to_schema() for non-DefaultVal fields - #730

Open
gg-sr wants to merge 1 commit into
getml:mainfrom
gg-sr:schema-no-default-val
Open

gg-sr wants to merge 1 commit into
getml:mainfrom
gg-sr:schema-no-default-val

Conversation

@gg-sr

@gg-sr gg-sr commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Some structs may be DefaultVal (and indeed have default values), but cannot be added automatically to a schema (because their default cannot be converted to a ReflectionType). This skips these values when creating schemas.

Also properly pass processors when computing the default, so e.g. naming matches the schema.

@gg-sr
gg-sr force-pushed the schema-no-default-val branch from ede821e to 29a3508 Compare September 29, 2026 02:08
Also properly pass processors when computing the default, so
e.g. naming matches the schema.
@gg-sr
gg-sr force-pushed the schema-no-default-val branch from 29a3508 to 1e29750 Compare September 29, 2026 02:30

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