Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: allow custom top-level properties in configuration schema #488

Merged
merged 2 commits into from
Oct 1, 2024

Conversation

alexander-held
Copy link
Member

The config schema has previously been very restrictive, not allowing unknown top-level properties. The intention was to help catch possible spelling mistakes, but at the top level this seems less likely and restricts the config when users may want to add custom information to the same file. To facilitate such use cases, allow for custom keys at the top level.

* allow custom top-level properties in configuration schema

Copy link

codecov bot commented Oct 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (d410d35) to head (88b2e41).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #488   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines         2093      2093           
  Branches       346       346           
=========================================
  Hits          2093      2093           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@alexander-held alexander-held force-pushed the feat/schema-top-block-restriction branch from 6fcfb2d to 88b2e41 Compare October 1, 2024 17:28
@alexander-held alexander-held merged commit 8f78894 into master Oct 1, 2024
8 checks passed
@alexander-held alexander-held deleted the feat/schema-top-block-restriction branch October 1, 2024 17:47
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