Repository navigation
feat(site): show source-backed stdin fixtures on individual lesson pages - #61
Merged
Merged
Conversation
sanskarIN
marked this pull request as ready for review
November 10, 2026 15:03
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
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.
Summary
When a numbered lesson has an optional adjacent
.stdinfixture, its generated static page now shows the supplied input as escaped, readable text, links to the raw fixture and provides a locally runnable stdin-redirection command. Lessons without an input fixture preserve the existing layout and commands.Changes
.stdinfile.scarp verify, which never consumes input.Compatibility and scope
The course still pins Scarp v0.0.6-alpha.4. This PR adds no alpha.6-only
read_lineexamples, does not change lesson counts or shipped.stdoutfixtures, and does not execute Scarp in the browser. Actual input lessons must wait for the released compiler migration and source/stdout provenance validation.Validation
Coordination
Requires merged PR #60 (already on main). Review with course migration PR #57 if it edits the same site-generation tests; retain both provenance and input-test coverage.