Skip to content

fix verbosity_assertions in the non-ini config format#5445

Merged
madskristensen merged 2 commits intoSchemaStore:masterfrom
DetachHead:patch-3
Mar 9, 2026
Merged

fix verbosity_assertions in the non-ini config format#5445
madskristensen merged 2 commits intoSchemaStore:masterfrom
DetachHead:patch-3

Conversation

@DetachHead
Copy link
Contributor

@DetachHead DetachHead commented Mar 6, 2026

verbosity_assertions in the new config format does not accept integers. attempting to set it to an int results in the following error at runtime:

config option 'verbosity_assertions' expects a string, got int: 2

@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

Thanks for the PR!

This section of the codebase is owned by @madskristensen and @hyperupcall - if they write a comment saying "LGTM" then it will be merged.

when setting it to an integer it crashes at runtime:

```
config option 'verbosity_assertions' expects a string, got int: 2
```
@DetachHead DetachHead changed the title fix verbosity_assertions not allowing numbers in string format in the non-ini config format fix verbosity_assertions in the non-ini config format Mar 6, 2026
@madskristensen madskristensen merged commit 85cecd8 into SchemaStore:master Mar 9, 2026
4 checks passed
@madskristensen
Copy link
Contributor

Thanks

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