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
HOTFIX: Achieve 100% doc coverage #1387
HOTFIX: Achieve 100% doc coverage #1387
Conversation
@@ -71,7 +71,7 @@ def example_group_started(notification) | |||
# | |||
# Invoked at the beginning of the execution of each example. | |||
# | |||
# @param notification [ExampleNotification] containing example subclass of `RSpec::Core::Example` | |||
# @param [ExampleNotification] notification containing example subclass of `RSpec::Core::Example` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ultimately, I just care about how this renders when you run a yard server (e.g. yard server --reload
). Did you confirm that it renders wrongly before and correctly with this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
weird thing is - this still renders correctly if you do it the other way (like @JonRowe did)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Funny. I think I actually prefer the @param <name> [<Type>] <description>
form because with this way, the name and description run together and it's non-obvious the first word is the param name.
That said, yard issues warnings for that and I care more about being warning free, so changing it like you have is the right thing to do :).
Thanks for following up on this, @yelled3! |
HOTFIX: Achieve 100% doc coverage
Thanks again! |
fixing some YARD formatting issues + pull from master