Skip to content

Accept None values for table config#50

Merged
martinv13 merged 1 commit intomainfrom
fix/add_check_none_table_config
Mar 19, 2026
Merged

Accept None values for table config#50
martinv13 merged 1 commit intomainfrom
fix/add_check_none_table_config

Conversation

@martinv13
Copy link
Copy Markdown
Collaborator

It can be the case that a table is explicitly configured with a None value in the config dict (e.g., from a YAML config file where a key exists but has no value).

This PR considers this possibility by simply checking for None values and replacing them with {}

One test case was added.

Solves #48

@martinv13 martinv13 merged commit 4691f70 into main Mar 19, 2026
9 checks passed
@martinv13 martinv13 deleted the fix/add_check_none_table_config branch March 19, 2026 14:25
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