Docs: Fix missing boolean types in full usage #2693
Merged
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
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.
Noticed while working on #2678 an assertion failure for which the fix is applicable to
master. Can see the difference for example formrconvert -bvalue_scalingoption, which currently does not report a type in__print_full_usage__.Raises a secondary question. Just as the RST documentation is generated and stored within the repository and CI then re-generates and cross-checks against that content, there is an argument to be made for the full interface definitions generated by
__print_full_usage__to be stored within the repository also (as has been argued for the Pydra interfaces in #2665).