Add API page #268
Merged
Add API page #268
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Mergifyio backport humble iron |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Apr 16, 2024
(cherry picked from commit 159087e) # Conflicts: # index.rst
mergify bot
pushed a commit
that referenced
this pull request
Apr 16, 2024
(cherry picked from commit 159087e) # Conflicts: # index.rst
christophfroehlich
added a commit
that referenced
this pull request
Apr 16, 2024
(cherry picked from commit 159087e) # Conflicts: # index.rst
christophfroehlich
added a commit
that referenced
this pull request
Apr 16, 2024
* Add API page (#268) (cherry picked from commit 159087e) # Conflicts: # index.rst * remove pid controller * Remove merge conflicts --------- Co-authored-by: Christoph Fröhlich <[email protected]>
mergify bot
added a commit
that referenced
this pull request
Apr 16, 2024
* Add API page (#268) (cherry picked from commit 159087e) # Conflicts: # index.rst * remove pid controller * Remove merge conflicts --------- Co-authored-by: Christoph Fröhlich <[email protected]> (cherry picked from commit 96b049e)
christophfroehlich
pushed a commit
that referenced
this pull request
Apr 16, 2024
* Add API page (#268) (cherry picked from commit 159087e) # Conflicts: # index.rst * remove pid controller * Remove merge conflicts --------- Co-authored-by: Christoph Fröhlich <[email protected]> (cherry picked from commit 96b049e) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'd like to include the API documentation of all packages, also for the utilities like control_toolbox etc.
I see two options:
Let rosdoc2 create the pages manually and publish a selection on control.ros.org. Advantage (or maybe also disadvantage?): Everything can be found from within a single search prompt.The majority was for option 1 during the WG meeting on April 10th. I changed it now to a simple table: