doc: reorder fs #2432
Closed
doc: reorder fs #2432
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
Sort in alphabetical order but keep *sync with their related functions. Classes follow functions. Events follow methods in classes.
brendanashworth
added
doc
|
cc @nodejs/documentation |
|
Should I close this? |
|
I'm +1 on this in principle, although I'd rather have there be some general rule for the ordering of properties established by @nodejs/documentation and applied across all the docs. Absent that, though, something that has an ordering principle is better than something that is in arbitrary order. |
|
For sure. I was thinking some headings may help and then alphabetical order within those. |
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.
Sort in alphabetical order but keep *sync with their related functions.
Classes follow functions.
Events follow methods in classes.