Run prettier on reference files as they are generated #65
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.
This does a bunch of leg work to have the reference files be reformatted (with prettier) as they are written. This makes the generation notably slower (slightly less than 1s -> slightly less than 4s on my machine), but saves from having to remember to run the formatting separately... which takes just as long as the extra time anyway.
This requires a few steps, broken across commits in a useful way (with some not-strictly-necessary changes), because prettier only has an async API. This seems to require running as an
.mjs
("module") rather than.js
to be able to useawait
at the top level.After getting to using async + prettier, this then makes a few changes that this allows:
Promise.all
(writing the targets and subsystems concurrently takes the time from ~4.4s -> ~3.8s, doing the others concurrently makes no difference, but makes the code look uniform).See also: #50 (comment)