Capability statement versions pulled from metadata - #128
Open
bryantaustin13 wants to merge 4 commits into
Open
bryantaustin13 wants to merge 4 commits into
bryantaustin13 wants to merge 4 commits into
Conversation
…ta, when that functionality exists.
Resolves conflicts in src/conf/config-loader.ts and src/shared/run-test-core.ts. Both were import-block only: main's TypeScript 7 migration (#124, #126) rewrote the imports in each file while this branch added imports to the same lines. The resolution keeps main's migrated style — the node: prefixes and the `import type` splits — and re-adds this branch's capability-statement imports alongside. No logic conflicted. Verified after resolution: tsc --noEmit clean, 224 tests passing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Currently cql-version and engine-version are not found in the metadata of a capability statement. If at some time in the future They are in that file this code is designed to pull that information into the runner. Right now it is using VERSION_URL = 'http://example.org/fhir/StructureDefinition/our-cql-version'; and similar. When an actual url is available, we need to substitute those with actual values. Currently the runner depends on configuration entries to supply the versions.