Repository navigation
S0329-parser-first-use-path: hold both first examples to a committed fixture and execute them - #90
Merged
Merged
Conversation
…fixture and execute them The record streams printed in the quickstart's first example and the README Usage example are committed byte for byte as test/fixtures/tier1-quickstart-result.astm and test/fixtures/tier1-readme-result.astm, inside the corpus pnpm phi-scan reads and the Tier-3 round-trip sweeps; the suites assert each example's stream is a copy. The quickstart's first block is checked to be the runnable block the sweep executes, run explicitly, with a changed-claim and a changed-input negative control. The README gate is pinned to the first fenced block under the Usage heading. Install commands in README.md and installation.md are compared with package.json name. No document text changed, so no changeset.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
… a backtracking regex CodeQL flagged the single pattern with a repeated group (exponential backtracking on a long run of empty literals). The literals are now read one at a time with a sticky pattern.
…s new TypeScript project does The snippet harness and tsx strip types without checking them, so pnpm test would stay green over a first-use example that does not compile. Both first examples now compile with the options tsc --init writes for a new project (strict, noUncheckedIndexedAccess, exactOptionalPropertyTypes, verbatimModuleSyntax, NodeNext), against src/index.ts, and the suite fails on any error the example itself carries. Both compile today; each carries a control that drops the undefined guard on the first result and must be reported. The install-specifier reader also reads pnpm i, pnpm install, npm add and deno add npm:, stops a specifier at a full stop and skips a protocol specifier, so no printed form passes vacuously.
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
2 participants
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.
Spec: cosyte/cosyte pipeline/active/S0329-parser-first-use-path/spec.md (child: children/astm.md).
No document text and no parser behaviour changed, so there is no changeset and AC-AS8 has no finding to pin. pnpm test leaves git status --porcelain empty.