feat: expose the full config to handlers#509
Conversation
Instead of just passing the handler_config on initialization pass the full dictionary of `extension_config` directly to the handler. References: mkdocstrings#501
@pawamoy interested to see where else you would see/want refactoring from having access to the full configuration object. Keeping the same interfaces/backwards compatibility limited a few other places that I saw. Namely in the |
|
Hey sorry, I forgot about this PR. Just so you know, it is fine to ping me if I don't answer 🙂 |
No worries, we are all busy! |
|
@pawamoy , I'll ping you this time. Did you get a chance to review? |
pawamoy
left a comment
There was a problem hiding this comment.
OK lets start with that and I'll see later if there's a way to push it even further. Thanks!
|
Sounds great, thanks! |
Instead of just passing only the handler_config on initialization pass the full dictionary of
extension_configdirectly to the handler. Refactors items that were pulled from the full configuration to point directly to that object.References: #501