Repository navigation
Write Cosyte with a capital C; bring the docs status and install note current for 0.1 - #60
Merged
Merged
Conversation
Decision 0001 (its title and context) and docs-content/concepts-archetype.md named the parser tier in lowercase; each 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
docs-content/intro.md still described the pre-0.1 package: "pre-alpha (0.0.x) ... cannot be installed from npm yet", and under Install, "That command does not work yet: @cosyte/fhir is not on the registry". All three packages are on npm at 0.1.0, and npm install @cosyte/transform @cosyte/hl7 @cosyte/fhir installs them in a fresh directory. The status now matches the README: 0.1, published to npm, and below 1.0 a breaking change ships in a minor version and is called out in the changelog. The sentence "The v2->FHIR direction is feature-complete for the IG-covered message set" is removed from the status blocks of the intro and the README. The blocks still list what the release ships. 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 parser tier prose
Decision 0001 (its title and context) and docs-content/concepts-archetype.md named the parser tier in lowercase; each 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 block and install note current for 0.1
docs-content/intro.md still described the pre-0.1 package: "pre-alpha
(0.0.x) ... cannot be installed from npm yet", and under Install, "That
command does not work yet: @cosyte/fhir is not on the registry". All three
packages are on npm at 0.1.0, and npm install @cosyte/transform
@cosyte/hl7 @cosyte/fhir installs them in a fresh directory. The status
now matches the README: 0.1, published to npm, and below 1.0 a breaking
change ships in a minor version and is called out in the changelog.
The sentence "The v2->FHIR direction is feature-complete for the
IG-covered message set" is removed from the status blocks of the intro and
the README. The blocks still list what the release ships.
https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9