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

Configuration object / knob #431

Open
tony opened this issue Sep 17, 2022 · 0 comments
Open

Configuration object / knob #431

tony opened this issue Sep 17, 2022 · 0 comments

Comments

@tony
Copy link
Member

tony commented Sep 17, 2022

Their should be a configuration object

Default / regular usage should never need to use it

But for any implied defaults, their should always be a way to override them. These should be tested and documented, with examples

The configurations should also allow overriding at the object level, in an overlay / patching style. Where the uppermost configuration knows are inherited but can be overridden at a lower level

Similar to pytest fixture overrides, except dealing with a configuration object specifically, rather than tests

image

image

image

image

Though these configuration knobs would make various types of testing easier

And also, the "override" at the object level would be perfect for context managers

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

No branches or pull requests

1 participant