Changed Inline Documentation Order #69145
Closed
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
shail-mehta
added
the
[Type] Developer Documentation
|
Maybe this is something that can be "enforced" by a linter. It would be hard to avoid order mismatches manually, and fixing them isn't a high priority. The JSDoc block parsers don't care about order, and documentation sites always use pre-determined data layouts. Just wanted to share some thoughts. I don't mind approving similar PRs, but similar rules are hard to maintain without a linter. |
|
Size Change: 0 B Total Size: 1.84 MB ℹ️ View Unchanged
|
shail-mehta
force-pushed
the
change-inline-documentation-order
branch
from
b97a75f to
0f3495d
Compare
|
Noted @Mamaduka Closing this PR. |
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.
What?
How?
@seetag before@paramtag)Testing Instructions