51 all code needs documentation - #52
Merged
Merged
Conversation
…ethods that aren't async
Owner
Author
|
I'd like to not be the one to review this. I'm going to ask random strangers if they've got time to review a PR. |
…e overwritten. Also reorganizes slightly so that similar things are together.
kelsS
reviewed
Jun 8, 2026
|
@paceaux LGTM except a possible typo I found |
This file contains hidden or 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
2 participants
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.
No code changes here. This could arguably be a minor version release?
This is just to make sure that everything is JSDoced. The project doesn't use TS because it isn't a library getting used by other properties / projects. But we do want consistent documentation for the code.