You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: