Add general CLI utilities and expand tests #2
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
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.
This adds most of the tools from our discussion yesterday, though I left a few out that were harder to figure out.
I also made some changes to the tests. The main motivation here was that the Node.js test framework supports running tests in parallel, but only file-by-file. With the tests spread out over multiple files like this, it speeds things up significantly.
I considered another strategy, which would be to define all the tests in one place, and then have a
tests/shard1.test.ts,tests/shard2.test.ts, etc. I decided that I didn't like the inflexibility of that, and would rather have the tests grouped by topic.