Please check if the PR fulfills these requirements
[X] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Supersedes set in CGMES metadata models (SSH) can not be emptied by the user.
This creates a problem when trying to export CGMES data for a network that is read from CGMES inputs that already specify superseding info.
In CGM quick export, the previous supersede and the one added automatically during export are present in the output.
In manual export, the user may add a supersede to the model, to prepare the export, but the previous supersede can not be removed. The exported files contains two supersede items.
What is the new behavior (if this is a feature change)?
The CGMES metada model supersedes set in the network extension can be emptied with the method CgmesMetadataModel::clearDependencies.
The quick CGM export clears the existing SSH supersedes before adding the current one.
For the manual export of single files, the user is now being able to clear previous supersedes before adding the requested one:
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Supersedes set in CGMES metadata models (SSH) can not be emptied by the user. This creates a problem when trying to export CGMES data for a network that is read from CGMES inputs that already specify superseding info.
In CGM quick export, the previous supersede and the one added automatically during export are present in the output.
In manual export, the user may add a supersede to the model, to prepare the export, but the previous supersede can not be removed. The exported files contains two supersede items.
What is the new behavior (if this is a feature change)?
The CGMES metada model supersedes set in the network extension can be emptied with the method
CgmesMetadataModel::clearDependencies
.The quick CGM export clears the existing SSH supersedes before adding the current one.
For the manual export of single files, the user is now being able to clear previous supersedes before adding the requested one:
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
If you had define a custom
CgmesMetadataModel
implementation, you need to define a new method:CgmesMetadataModelImpl clearSupersedes()
.Other information: