Add getI() method to DanglingLine's boundary

[caioluke]

Please check if the PR fulfills these requirements

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

Feature

What is the current behavior?

Boundary nodes do not have a getI() method, whereas terminals do. Therefore, for paired dangling lines, we can not get the current from both sides of the half line easily.

What is the new behavior (if this is a feature change)?
Add the getI() method for boundary nodes.

Does this PR introduce a breaking change or deprecate an API?

• Yes
• No

If yes, please check if the following requirements are fulfilled

• The Breaking Change or Deprecated label has been added
• The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Custom IIDM implementations that are implementing the Boundary interface (which is not necessarily the case) should add the following method to their implementation:

• double getI();

[jeandemanged]

Hi @olperr1 ,
One question, I am not so sure this should be flagged "Breaking Change". Unless there are iIDM implementations around overriding the default "utils" calculations that are built-in the iIDM API. But I don't think implementations should do that ...
Your opinion ?

[olperr1]

Hi @olperr1 , One question, I am not so sure this should be flagged "Breaking Change". Unless there are iIDM implementations around overriding the default "utils" calculations that are built-in the iIDM API. But I don't think implementations should do that ... Your opinion ?

Hi @jeandemanged,
You are right, I was misled by the interface's package. It is not used by network elements, but only by utils. I will remove the label.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[olperr1]

I double-checked the Boundary interface usage and I found that powsybl-network-store has its own implementation (which is very similar to the powsybl-core one, but its an other problem). So I will report this change as a breaking change.