Changes to be able to generate FHIR R6.#61
Merged
ewoutkramer merged 2 commits intomainfrom May 23, 2025
Merged
Conversation
andrzejskowronski
previously approved these changes
May 23, 2025
Small correction in name of one of the launchsettings
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
2 participants
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.
These are the changes to the generator so we can run FHIR R6 generation. Note that we have no support for the "resoure" search param type yet. Also, there are mistakes in ballot3 for insummary and there is an operation with a duplicate searchparam. Also, we cannot yet use R6 for generating Base + Conformance (insummary, changed location of some enums, strings turned into markdown.).
But at least, we will have the code in the generator, so we can play with R6 when we need it.