The command devbox generate readme ignores the order of the scripts and re-orders it in the readme file to alphabetical order. I use the order explicitly for the humans who read it, so they have a clue what to do first.
Example of the problem
Scripts
The devbox.json with the scripts in a particular order:
For now I prepend the script name with a number, but this is cumbersome for maintenance. Because when an extra step is requirement somewhere in between, the next script names also has to change. This is not great...
What problem are you trying to solve?
The command
devbox generate readme
ignores the order of the scripts and re-orders it in the readme file to alphabetical order. I use the order explicitly for the humans who read it, so they have a clue what to do first.Example of the problem
Scripts
The
devbox.json
with the scripts in a particular order:Generated README.md
This is the generated readme file created with
devbox generate readme
:Scripts
Scripts are custom commands that can be run using this project's environment. This project has the following scripts:
Script Details
devbox run step-four
devbox run step-one
devbox run step-three
devbox run step-two
What solution would you like?
The generated Markdown in the
README.md
file should have the same order as in thedevbox.json
file, like so:Scripts
Scripts are custom commands that can be run using this project's environment. This project has the following scripts:
Script Details
devbox run step-one
devbox run step-two
devbox run step-three
devbox run step-four
Alternatives you've considered
For now I prepend the script name with a number, but this is cumbersome for maintenance. Because when an extra step is requirement somewhere in between, the next script names also has to change. This is not great...
Example of alternative
Generated README.md
Scripts
Scripts are custom commands that can be run using this project's environment. This project has the following scripts: