-
Notifications
You must be signed in to change notification settings - Fork 1
Add docs for ni.protobuf.types and a workflow to generate docs. #28
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
Signed-off-by: Michael Johansen <[email protected]>
Signed-off-by: Michael Johansen <[email protected]>
Signed-off-by: Michael Johansen <[email protected]>
Signed-off-by: Michael Johansen <[email protected]>
Co-authored-by: Brad Keryan <[email protected]>
Signed-off-by: Michael Johansen <[email protected]>
Signed-off-by: Michael Johansen <[email protected]>
Signed-off-by: Michael Johansen <[email protected]>
Try setting |
In measurement-plugin-python we had to use autoapi-skip-member to handle classes that are exported from multiple modules, but I don't know why sphinx-autoapi thinks these types are imported in waveform_conversion. https://github.com/ni/measurement-plugin-python/blob/main/packages/service/_docs_source/conf.py#L57 |
Setting |
I think it has something to do with the custom template I implemented. If I comment out Then the imported types don't get shown. However, then we are back at our original problem of everything being |
I think the custom template removes some logic from the original template that we still want. You should compare the original and custom templates and see what's missing. |
…m exclusions for classes in conversion python files. Signed-off-by: Michael Johansen <[email protected]>
Signed-off-by: Michael Johansen <[email protected]>


What does this Pull Request accomplish?
Add the following files to a
docsfolder underpackages/ni.protobuf.types:Add a new workflow file
check_docs.ymlthat takes a package name input and creates/uploads the docs for that package using sphinx. I also added a new step inCI.ymlto call into this new workflow.Why should this Pull Request be merged?
Implements part of AB#3166742
What testing has been done?
I generated the docs manually and performed a visual inspection. They look pretty good considering most of the functions are code-generated.