Skip to content

Fill in default config values when key is missing from database#776

Merged
goto-bus-stop merged 2 commits into
defaultfrom
fill-config-defaults
May 14, 2026
Merged

Fill in default config values when key is missing from database#776
goto-bus-stop merged 2 commits into
defaultfrom
fill-config-defaults

Conversation

@goto-bus-stop
Copy link
Copy Markdown
Member

Previously we'd just use an empty object, but this might not be a valid
value if the schema specifies required properties. If those required
properties have defaults, we can fill them in like this.

Also verify that an empty object is valid for every registered config schema,
so you can't have a schema that would cause errors when the client tries to render it.

Previously we'd just use an empty object, but this might not be a valid
value if the schema specifies required properties. If those required
properties have defaults, we can fill them in like this.

Also verify that an empty object is valid for every registered config schema,
so you can't have a schema that would cause errors when the client tries to render it.
@coveralls
Copy link
Copy Markdown

coveralls commented May 14, 2026

Coverage Status

coverage: 68.408% (+0.04%) from 68.367% — fill-config-defaults into default

@goto-bus-stop goto-bus-stop enabled auto-merge (squash) May 14, 2026 14:43
@goto-bus-stop goto-bus-stop merged commit c68c069 into default May 14, 2026
8 checks passed
@goto-bus-stop goto-bus-stop deleted the fill-config-defaults branch May 14, 2026 14:44
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.

2 participants