Run the README, as printed - #12
Merged
Merged
Conversation
The block at the top of the page is the most read and least executed code this package has. It is copied by hand, and it goes wrong quietly: a renamed option, a return type that used to be an array, a statement the grammar stopped taking. By the time anybody notices, it has already cost somebody their first five minutes. So it runs now, character for character, in a directory of its own with this package linked into node_modules the way npm links it. The import is the one a reader types and the database lands where a reader would find it. Node erases the types on the way in, which is why the block can stay TypeScript, which is what a reader of a typed client copies. A block is a whole program when its first line imports this package and nothing in it calls require. The page has one of those and six fragments, and the count is asserted, so a block that changes which kind it is fails here rather than falling out of the check. Bun and Deno skip the two tests that spawn a runtime, and run the one that reads the page. What is being asked about is the characters on the page, and one runtime answers it.
This file contains hidden or 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
1 participant
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.
The block at the top of the page is the most read and least executed code this package has. It is copied by hand, and it goes wrong quietly: a renamed option, a return type that used to be an array, a statement the grammar stopped taking. By the time anybody notices, it has already cost somebody their first five minutes.
So it runs now, character for character, in a directory of its own with this package linked into
node_modulesthe way npm links it. The import is the one a reader types and the database lands where a reader would find it. Node erases the types on the way in, which is why the block can stay TypeScript, which is what a reader of a typed client copies.A block is a whole program when its first line imports this package and nothing in it calls
require. The page has one of those and six fragments, and the count is asserted, so a block that changes which kind it is fails here rather than falling out of the check.Bun and Deno skip the two tests that spawn a runtime and run the one that reads the page. The link is a junction rather than a symbolic link, which is what npm makes on Windows, because a symbolic link to a directory needs a privilege there that a test runner does not have.
This is the
quickstartline of the practice scorecard, which zu-python already holds.