Fix various documentation errors in tf2 (backport #857) #864
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Generated-by: Portions of this commit may include code completion from github.copilot version 1.372.0 or later
Description
This PR fixes various issues causing errors in the rosdoc2 documentation of tf2. Most are just fixes around individual function documentations.
Probably the most important change is in tf2/Doxyfile. Without this, the widely-used
Vector3class is not being documented, and references to its use cause complaints.Although this PR does not depend on #856, I recommend that you land that first to get consistent rosdoc2 results.
This PR partially addresses #833
Is this user-facing behavior change?
This only affects documentation generation by rosdoc2
Did you use Generative AI?
See the header.
Additional information.
Two errors remain in documentation. One is a complaint about None as a language, which will be fixed in a pending PR to redo the conf.py files. The other is:
This comes from
tf2/include/tf2/impl/convert.hppand the declarations like:rosdoc2 document generation does not appear to be able to detect
Converter<true, true>andConverter<true, false>as separate function types. I have not been able to devise a fix for this.This is an automatic backport of pull request #857 done by Mergify.