-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
translate voltagelevel with substation creation modification label #699
translate voltagelevel with substation creation modification label #699
Conversation
@ghazwarhili there was a conflict on this PR : it was simple and you were not there so I solved it myself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code and Test ok except for older network modification because there is no migration yet. But I can see that it is explained in the ticket. Where do you plan to add it ?
Anyway I think migrating this is not a big deal, is it ?
@@ -27,6 +27,8 @@ interface ModificationValues { | |||
energizedVoltageLevelId: string; | |||
equipmentAttributeName: string; | |||
equipmentAttributeValue: string; | |||
voltageLevelEquipmentId: string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I already said it in the back but I think equipmentId
is enough and should be used for the main equipment id.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer to use voltageLevelEquipmentId to be coherent with the new VOLTAGE_LEVEL_CREATION_SUBSTATION_CREATION type
confirmed with @etiennehomer : no migration needed. |
…tion-voltageLevel-with-substation-creation' into implement-specific-label-translation-voltageLevel-with-substation-creation
…Level-with-substation-creation
|
No description provided.