Repository navigation
docs: say what the round trip checks - #70
Merged
Merged
Conversation
Where the README and docs-content called every artifact "spec-clean by construction", they now say what the round-trip harness checks: each artifact is built through its parser's own builder or serializer and re-parses through that parser with zero warnings. The HL7 v2, FHIR and C-CDA sections, and the 837P and NewRx guide headings, are unchanged. - README: tagline, overview, status, the X12, NCPDP and ASTM headings and corpus comments, the deid loop, and the design list. - intro, concepts, troubleshooting, guides overview, the X12, NCPDP, ASTM, deid and quirk guides, limitations, and the generate-every-format example docblock. Checked on the published 0.1.0 from a clean install: over seeds 1 to 25, the HL7 ADT, FHIR Patient, CCD, 837P, 835, 271, NewRx, B1 and ASTM result (plain and framed) round trips report zero warnings and are byte-stable. Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
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.
Where the README and docs-content called every artifact "spec-clean by construction", they now say what the round-trip harness checks: each artifact is built through its parser's own builder or serializer and re-parses through that parser with zero warnings, byte-stable. The HL7 v2, FHIR R4 and C-CDA sections, and the 837P and NewRx guide headings, keep their wording. The
specCleanproperty and every code comment that prints exactly what the API returns are unchanged.Checked on the published
@cosyte/synth0.1.0 (with the six 0.1.x parsers) from a clean install outside any repository: over seeds 1 to 25,roundTrip/scriptRoundTrip/telecomRoundTrip/astmRoundTrip/astmFramedRoundTripon the HL7 ADT, FHIR Patient, CCD, 837P, 835, 271, NewRx, B1 and ASTM result (plain and framed) report zero warnings and are byte-stable.// true, all spec-clean// trueNo runnable block changes (the README HL7 block that
docs-content.test.tscompares with the quickstart is untouched), and the floors sectionfloor-citations.test.tsreads is untouched. No link targets the renamed headings.prettier --checkpasses on README.md and the example. The package.jsondescriptionchanges only with a release.https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9