-
Notifications
You must be signed in to change notification settings - Fork 709
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
Ability to sort entry points #2393
Comments
Hmm... how does this play with people who specify wildcards as entry points? Glob expansion order isn't generally specified & depends on your OS. Currently, everything is sorted with the --sort option. |
Just some way to mandate/hardcode a certain order at any level of the nav would be great. If I come up with a good idea I'll post it here. Perhaps some kind of array of item names that are ordered with top priority before the other sorting rules. |
I suppose a |
That would work! |
Thanks @Gerrit0! |
Search Terms
entry point, sort, sorting
Problem
I'm supplying a list of separate entry points (which map to different NPM package exports), and I'd like to make sure they appear in the generated docs in a certain order. One of the exports is the main export of the package, and I want that one at the top to emphasize that fact. The others are used in special circumstances only.
Currently the generated docs sort them in alphabetical order.
Suggested Solution
Perhaps the order that you supply entry points in the
entryPoints
array should dictate the order they appear in the generated docs.The text was updated successfully, but these errors were encountered: