-
Notifications
You must be signed in to change notification settings - Fork 43
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
cim:Jumper support #3235
cim:Jumper support #3235
Conversation
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
...s/cgmes-conversion/src/test/java/com/powsybl/cgmes/conversion/test/JumperConversionTest.java
Outdated
Show resolved
Hide resolved
} else if (type.contains("jumper")) { | ||
return SwitchKind.DISCONNECTOR; |
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.
The property bag has for "type" the whole value with the namespace (type -> http://iec.ch/TC57/2013/CIM-schema-cim16#Jumper), but getLocal removes the namespace prefix. In the end, the value we get is exactly the class name. So I guess we could test with "jumper".equals(type) instead.
However, I propose we do it in a separate PR. That way we can change it for all switch types.
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
Quality Gate passedIssues Measures |
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No, but a slack user did request it
What kind of change does this PR introduce?
feature
What is the current behavior?
cim:Jumper are ignored at CGMES/cim import
What is the new behavior (if this is a feature change)?
cim:Jumper are imported as disconnectors
Does this PR introduce a breaking change or deprecate an API?