Rework adding elements to a component version #844
Merged
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.
What this PR does / why we need it:
The previous mechanism for adding elements (resources, sources and references) to a component version
provided a hybrid mechanism, only:
This behaviour does not allow to add elements with the same base identity but a different version, if the version
is not explicitly added to the extra identity.
So, far this explicit handling of the version is not required, because it is implicitly done when evaluating the element list.
This PR add new options to the Set methods for the three element kinds on the component version access to specify the exact desired behaviour:
The default behaviour is unchanged. It is sufficient for the most common use cases, as long as no
duplicate entries with different versions should be added.
The CLI commands have been adjusted to use the Append mode by default. This is exactly what is desired if new component versions are composed.
If an existing version should be modified, it is possible to use the option
-R
to switch to the default mode.Which issue(s) this PR fixes:
Fixes #842