Repository navigation
Conversation
This is required when building using python -m sphinx docs/source docs/build from the root of the project
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #73 +/- ##
=======================================
Coverage ? 47.18%
=======================================
Files ? 12
Lines ? 960
Branches ? 204
=======================================
Hits ? 453
Misses ? 467
Partials ? 40
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@AA-Turner do you have time to review this PR please? |
|
Hi @AA-Turner, is there anything I can do here? The paths are currently always resolved from the CWD instead of the sphinx build dir. This makes building the docs dependent on being in the correct folder when calling |
|
@maurerle you are absolutely right here. This would resolve #87 (I just created it). However, I don't agree in trying multiple path-resolves until one succeeds. Although maybe convenient in some cases, it could technically result in the wrong file being used without the developer ever knowing. Instead I would say we only use the path relative to the source dir, since this would provide a stable result. What do you think? EDIT: See new PR, #88 |
|
Sure, if you mark your PR as ready, I will close this. I think it is better to clean this up. I just added the sane case in front, as there were already a few. |
|
@RobertoRoos could we please get a new release with this fix? |
|
Yeah, that was well overdue. New release |
This is required when building using
python -m sphinx docs/source docs/buildfrom the root of the project.
I would like to refactor this section to use pathlib though.