Skip to content

apply CompositeModification#156

Merged
Mathieu-Deharbe merged 17 commits intomainfrom
apply-composite-modification
Feb 20, 2026
Merged

apply CompositeModification#156
Mathieu-Deharbe merged 17 commits intomainfrom
apply-composite-modification

Conversation

@Mathieu-Deharbe
Copy link
Contributor

@Mathieu-Deharbe Mathieu-Deharbe commented Feb 4, 2026

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

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>
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
Mathieu-Deharbe and others added 2 commits February 13, 2026 10:11
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
public class CompositeModificationInfos extends ModificationInfos {

@Schema(description = "composite modification name")
private String compositeName;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

who say this forbidden sonar?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 "?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's better because it's already what we used in other entities or DTO.

Mathieu-Deharbe and others added 2 commits February 17, 2026 10:24
Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
@flomillot flomillot self-requested a review February 18, 2026 14:12
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}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe something more nested ? Like it's done for tabular modifications.

network.modification.tabular.creation = Tabular creation: ${modificationsCount} ${defaultMessage}
network.modification.tabular.creation.error = Tabular creation: No ${defaultMessage}
network.modification.tabular.creation.exception = ${message}
network.modification.tabular.creation.equipmentId = Creation of ${equipmentId}
network.modification.tabular.creation.error.equipmentError = Creation errors

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done : cf2ddb4

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}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
network.modification.composite.reportException = Cannot execute ${modificationName} : ${errorMessage}
network.modification.composite.exception.report = Cannot execute ${modificationName} : ${errorMessage}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done : 0362d7c

Signed-off-by: Mathieu DEHARBE <mathieu.deharbe@rte-france.com>
@sonarqubecloud
Copy link

@Mathieu-Deharbe Mathieu-Deharbe merged commit eec1b82 into main Feb 20, 2026
3 checks passed
@Mathieu-Deharbe Mathieu-Deharbe deleted the apply-composite-modification branch February 20, 2026 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants