-
Notifications
You must be signed in to change notification settings - Fork 17
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
Schema for choices results in validation error #287
Comments
Support for that has been added a long time ago. Which version of antsibull-docs is used to produce that error? Do you have some kind of logs to look at? |
Also as you can see on the devel docsite, this is rendered correctly: https://docs.ansible.com/ansible/devel/collections/ansible/builtin/package_facts_module.html#parameter-manager |
@felixfontein Sigh, my bad. Apparently it was just my environment and likely an older version of antsibull-docs ( |
No worries, I'm glad this is now resolved :) |
Thanks. There were some similar errors in the package docs build (some logs). But, yeah, I should have made sure the issue was reproduced somewhere other than my laptop. |
Quite a few warnings do not concern antsibull-docs generated stuff btw. Looks like some cleanup should be done, and potentially some error-checking isn't properly working / skipping community-only files:
|
Some interesting messages related to antsibull-docs:
|
Yeah I plan to bring this up at the next DaWGs actually. I'd actually love to get package docs to the point where we can configure Sphinx to fail on WARNING and then set up nightly build runs so we can get notified early and fix things. I guess there will be a lot of things to fix before we get to that point. However, I would like to see that as part of the collection inclusion convenant / agreement - collection docs must not produce any errors or warnings in the package docs build. |
Antsibull-docs throws a validation error during Sphinx build for the core docs due to the format of choices in the
package_facts
module.This is the validation error:
Follows on from ansible/ansible#83495
Seems related to #276
The text was updated successfully, but these errors were encountered: