Set version based on sushi-config.yaml in FSHOnly projects #1456
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.
Fixes #1380
This PR adds back support for using the version specified in
sushi-config.yaml
in Structure Definitions, Value Sets, and Code Systems as a default value in FSH Only projects. If theversion
is set with a rule, that will overwrite the version from the config file. This is only done in the case whereFSHOnly
is set totrue
in the config file because the IG Publisher will set the version when it is used.Because
status
is already set using the value insushi-config.yaml
as a default in all projects, this should restore the functionality that was removed in SUSHI 3.x. As a reference, I was looking at PR #1143, which removed this functionality originally.