Skip to content
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

Docs build fixes #45

Merged
merged 6 commits into from Mar 20, 2024
Merged

Docs build fixes #45

merged 6 commits into from Mar 20, 2024

Conversation

lkubb
Copy link
Contributor

@lkubb lkubb commented Nov 15, 2023

Fixes: #44

Based on #42 because there are no requirement files to fix in this repo before merging it

* do not strip module names from file paths in `make-autodocs`
* do not tell `sphinx-autosummary` to generate its own stubs
* work with `no_saltext_namespace`
* report exit status >0 if something changed for pre-commit
__file__ is not set in GH workflows and needlessly complex
Copy link
Member

@s0undt3ch s0undt3ch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still a valid and wanted PR?

@s0undt3ch s0undt3ch self-assigned this Jan 31, 2024
@lkubb
Copy link
Contributor Author

lkubb commented Jan 31, 2024

The underlying issue is still valid, without this the docs are pretty broken afair. If this tool is still intended to be the official way to create an extension, I think it should be fixed.

In the copier template, I included some additional changes built on top of this PR:

  • virtualnames as module doc headings, except for utils (import path here ofc)
  • include nested utils modules
  • removed docs/all.rst nesting by rendering the module index directly in docs/index.rst

I'm happy to contribute those in a separate PR if desired.

@s0undt3ch
Copy link
Member

If the copier template is better and more maintainable than this code, I'm in favor of advising users to use that instead.

@lkubb
Copy link
Contributor Author

lkubb commented Feb 8, 2024

I do think it's a bit more maintainable and easier to add new functionality to, in addition to allowing boilerplate updates for existing projects. We should probably transfer it into the salt-extensions org if it becomes an official recommendation though.

@s0undt3ch
Copy link
Member

A discussion should happen in the salt-extensions working group on which tool to send the users too. In the meantime, I'm merging in these fixes.

@s0undt3ch s0undt3ch merged commit 56d2384 into saltstack:main Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docs build borked
3 participants