docs: Fix spec objects parameter definitions #2024
Merged
+67
−25
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.
This PR fixes some issues with the docs on the recently added spec objects. When I got to some specs that only add one or two parameters to the subclass I forgot why I was using a
typedef
for the constructor parameters and wrote them inline. This was a mistake. Each subclass's parameters should augment the parent class's parameters. We can only do that withtypedef
blocks for the parameters.As I was fixing this issue, I discovered that the
@augments
tag does not inline the parent definition's properties, nor provide a link back to the definition. The@mixes
tag at least provides a link.