Add a YAML parsing simulator - #1702
Merged
Merged
Conversation
Deploying devops-daily with
|
| Latest commit: |
6b3b7ff
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://97609695.devops-daily.pages.dev |
| Branch Preview URL: | https://feat-yaml-parsing-simulator.devops-daily.pages.dev |
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.
Closes #1698.
Nothing on the site covered YAML, which is the most common way a DevOps change fails quietly.
The parser is real and runs in the browser (lib/games/yaml-sim-engine.ts, 24 assertions in the engine test). Every document is read twice, under YAML 1.1 and YAML 1.2, and the differences are listed, because the two specs disagree and that disagreement is where the surprises come from.
Eight lessons, all editable: the Norway problem, version 1.10 being lower than 1.9, leading zeros meaning octal in one spec and decimal in the other, empty against ~ against null against an empty string, block scalars, tabs, and the missing space after a colon. Then quoting, which is the fix for nearly all of it.
Registry validation passes for 56 games. No new tsc errors reference these files.