Conversation
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
src/main/java/org/gridsuite/modification/modifications/CompositeModification.java
Show resolved
Hide resolved
| public class CompositeModificationInfos extends ModificationInfos { | ||
|
|
||
| @Schema(description = "composite modification name") | ||
| private String compositeName; |
There was a problem hiding this comment.
Composite modifications need to be identifiable by a name in order to be displayed in gridstudy and in the execution logs. This will allow for the users to rename the composites and organize them as folders.
I called it compositeName instead of just name because name is a forbidden variable name.
There was a problem hiding this comment.
who say this forbidden sonar?
There was a problem hiding this comment.
Actually I just changed it back to just "name" and it seems to work fine. I don't remember what the problem was. Do you want me to change it to "name "?
There was a problem hiding this comment.
I think it's better because it's already what we used in other entities or DTO.
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
src/main/java/org/gridsuite/modification/dto/CompositeModificationInfos.java
Outdated
Show resolved
Hide resolved
src/main/java/org/gridsuite/modification/dto/ModificationsToCopyInfos.java
Show resolved
Hide resolved
src/main/java/org/gridsuite/modification/modifications/CompositeModification.java
Outdated
Show resolved
Hide resolved
| network.modification.limitSetAbsentOnSide1 = limit set '${selectedOperationalLimitsGroup}' on side 1 does not exist | ||
| network.modification.limitSetAbsentOnSide2 = limit set '${selectedOperationalLimitsGroup}' on side 2 does not exist | ||
| network.modification.composite = Composite modification : '${modificationName}' | ||
| network.modification.compositeReportException = Cannot execute ${modificationName} : ${errorMessage} |
There was a problem hiding this comment.
Maybe something more nested ? Like it's done for tabular modifications.
src/test/java/org/gridsuite/modification/modifications/CompositeModificationsTest.java
Show resolved
Hide resolved
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
| network.modification.limitSetAbsentOnSide1 = limit set '${selectedOperationalLimitsGroup}' on side 1 does not exist | ||
| network.modification.limitSetAbsentOnSide2 = limit set '${selectedOperationalLimitsGroup}' on side 2 does not exist | ||
| network.modification.composite.apply = Composite modification : '${modificationName}' | ||
| network.modification.composite.reportException = Cannot execute ${modificationName} : ${errorMessage} |
There was a problem hiding this comment.
| network.modification.composite.reportException = Cannot execute ${modificationName} : ${errorMessage} | |
| network.modification.composite.exception.report = Cannot execute ${modificationName} : ${errorMessage} |
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
|



enable the application of the composite modification (not yet possible to add them from the front, this is a pure back ticket, checked via unit tests and swagger)
adds a name to the composite modifications