-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
make it easier to use a different default theme #4278
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a reasonable change. I agree the theme should be set by a string that's passed in, instead of hard-coded. We'd want this to be configurable by a setting though, if we actually wanted it to be easily changed.
Updated PR, haven't touched settings because we can update the context via the |
ping |
Thanks for your PR.
I suppose this is the only thing missing to be in a "ready to merge" state. |
@humitos can we please merge this as is and if someone want to expose this with a setting just do another PR? I don't have much bandwidth to work on this and I think the code duplication reduction is worth on its own. |
That might be a good 'Good First Issue' to open, too. |
Tested this locally and it works well. Agreed the duplication is reason enough, and it can be changed via signal. 👍 |
@ericholscher thank you very much for skimming these old PRs, much appreciated |
This is for discussion more than inclusion. If this is sound we may want to do the same for default extensions. Our goal is to avoid the conf.py entirely in the documentation repos or make it very slim.