Skip to content
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

Adding inline documentation #16955

Merged
merged 1 commit into from Mar 21, 2022
Merged

Adding inline documentation #16955

merged 1 commit into from Mar 21, 2022

Conversation

jeremyf
Copy link
Contributor

@jeremyf jeremyf commented Mar 21, 2022

What type of PR is this? (check all applicable)

  • Documentation Update

Description

While exploring the DashboardsController, I came across method calls to
not_found. Idiomatically, I assumed that these methods were returning
a value. However, in looking at the code, it raises an exception.

Note: I excpect methods that raise exceptions, especially as the only
thing they do, to end in a !.

By adding the documentation my "IntelliSense" provides insight into the
expected behavior of this function (e.g. "Raises an exception").
Without the documentation, I don't see any useful information.

With Inline Docs

The "proposed" state:

eglot-with-inline-docs

Without Inline Docs

The "prior" state.

eglot-without-inline-docs

Related Tickets & Documents

QA Instructions, Screenshots, Recordings

None.

UI accessibility concerns?

None.

Added/updated tests?

  • No, and this is why: It's a documentation only PR.

[Forem core team only] How will this change be communicated?

  • I will share this change internally with the appropriate teams

While exploring the DashboardsController, I came across method calls to
`not_found`.  Idiomatically, I assumed that these methods were returning
a value.  However, in looking at the code, it raises an exception.

_Note: I excpect methods that raise exceptions, especially as the only
thing they do, to end in a `!`._

By adding the documentation my "IntelliSense" provides insight into the
expected behavior of this function (e.g. "Raises an exception").
Without the documentation, I don't see any useful information.
@jeremyf jeremyf requested a review from a team March 21, 2022 20:00
@pr-triage pr-triage bot added the PR: unreviewed bot applied label for PR's with no review label Mar 21, 2022
@jeremyf jeremyf requested a review from dscottS3 March 21, 2022 20:01
@pr-triage pr-triage bot added PR: partially-approved bot applied label for PR's where a single reviewer approves changes and removed PR: unreviewed bot applied label for PR's with no review labels Mar 21, 2022
@jeremyf jeremyf requested a review from a team March 21, 2022 20:50
Copy link
Contributor

@djuber djuber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

comment only changes are almost as nice as all red code changes!

@pr-triage pr-triage bot added PR: reviewed-approved bot applied label for PR's where reviewer approves changes and removed PR: partially-approved bot applied label for PR's where a single reviewer approves changes labels Mar 21, 2022
@jeremyf jeremyf merged commit 26149dd into main Mar 21, 2022
@jeremyf jeremyf deleted the jeremyf/adding-documentation branch March 21, 2022 21:18
@pr-triage pr-triage bot added PR: merged bot applied label for PR's that are merged and removed PR: reviewed-approved bot applied label for PR's where reviewer approves changes labels Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: merged bot applied label for PR's that are merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants