-
Notifications
You must be signed in to change notification settings - Fork 20
Add support for injecting dependencies #119
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
Add support for injecting dependencies #119
Conversation
Users of docs-as-code can now provide additional dependencies to the docs, and ide_support macros, to support use cases like project-specific sphinx-themes.
License Check Results🚀 The license check job ran with the Bazel command: bazel run //src:license-checkStatus: ✅ Passed Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
|
Adding to venv is fine. But I'm not sure about the other one. I don't think we want to allow arbitrary dependencies to docs. What's the use case here? |
|
My use case is to support different layouts, in our projects we're using sphinx-rtd-theme. Without additional dependencies, I wouldnt be able to make it available to sphinx. |
|
The design is rather intentional. You will also not be able to use any types which are not defined in score process, etc. Maybe you can get in contact with me or @MaximilianSoerenPollak via Slack? |
Users of docs-as-code can now provide additional dependencies
to the docs, and ide_support macros, to support use cases like
project-specific Pyhton packages.