Repository navigation
Write Cosyte with a capital C; docs status current for 0.1; name the parsers exporting toISO - #153
Merged
Merged
Conversation
docs-content/benchmarks.md called @cosyte/hl7 "the reference cosyte parser"; it now writes Cosyte. The operator, in their own words: "Uppercased C on Cosyte everywhere. Fix any location that has it as lowercase" The launch-ready name search now gives its cli-subcommand exclusion a word boundary, so prose such as "cosyte parser" no longer passes as the cli binary. Identifiers are unchanged: the @cosyte scope, cosyte/<repo> paths, heading anchors and URLs. Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
…ing toISO docs-content/installation.md and troubleshooting.md said the package was "still pre-alpha on the 0.0.x-until-first-alpha ladder", and the FHIR bridge's semver posture followed "the package's 0.0.x-until-first-alpha ladder". It is on npm at 0.1.0, and npm install @cosyte/hl7 installs in a fresh directory. Each now states the 0.1 policy: the exported functions, the message and helper surfaces and the 20 warning codes are the surface we keep stable, and below 1.0 a breaking change moves the minor version with the changelog saying how to migrate; the bridge's bullets apply from 1.0. README.md and docs-content/spec-notes-datetime-precision.md said toObject, toISO and toDate are identical in every @cosyte parser. Checked against the published packages: hl7, x12, dicom, ncpdp, astm and ccda export all three; @cosyte/fhir and @cosyte/mllp export none of them. Both sentences now name the six. 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
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.
Write Cosyte with a capital C in the benchmarks page
docs-content/benchmarks.md called @cosyte/hl7 "the reference cosyte parser"; it now writes Cosyte.
The operator, in their own words: "Uppercased C on Cosyte everywhere. Fix any location that has it as lowercase"
The launch-ready name search now gives its cli-subcommand exclusion a word
boundary, so prose such as "cosyte parser" no longer passes as the cli
binary. Identifiers are unchanged: the @cosyte scope, cosyte/ paths,
heading anchors and URLs.
Bring the docs status blocks current for 0.1; name the parsers exporting toISO
docs-content/installation.md and troubleshooting.md said the package was
"still pre-alpha on the 0.0.x-until-first-alpha ladder", and the FHIR
bridge's semver posture followed "the package's 0.0.x-until-first-alpha
ladder". It is on npm at 0.1.0, and npm install @cosyte/hl7 installs in a
fresh directory. Each now states the 0.1 policy: the exported functions,
the message and helper surfaces and the 20 warning codes are the surface we
keep stable, and below 1.0 a breaking change moves the minor version with
the changelog saying how to migrate; the bridge's bullets apply from 1.0.
README.md and docs-content/spec-notes-datetime-precision.md said toObject,
toISO and toDate are identical in every @cosyte parser. Checked against the
published packages: hl7, x12, dicom, ncpdp, astm and ccda export all
three; @cosyte/fhir and @cosyte/mllp export none of them. Both sentences now
name the six.
https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9