-
Notifications
You must be signed in to change notification settings - Fork 2
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
[IIDM V1.2] Removed duplicates in VoltageLevel::getConnectables (#46) #143
[IIDM V1.2] Removed duplicates in VoltageLevel::getConnectables (#46) #143
Conversation
BOOST_AUTO_TEST_CASE(getConnectablesCheckUnique) { | ||
const Network network = createLineTestNetwork2(); | ||
const VoltageLevel& vl = network.getVoltageLevel("VL1"); | ||
BOOST_CHECK_EQUAL(1UL, boost::size(vl.getConnectables<Line>())); |
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.
Could you check that vl.getConnectableCount()
also return 1
?
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.
You're right, it fails... I have to patch getConnectableCount() also
92fdb79
to
276df64
Compare
Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
…om a VL/substation Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
ab14754
to
9d05f88
Compare
… add tests Signed-off-by: Sébastien LAIGRE <slaigre@silicom.fr>
Kudos, SonarCloud Quality Gate passed! 0 Bugs |
Signed-off-by: Sébastien LAIGRE slaigre@silicom.fr
Please check if the PR fulfills these requirements (please use
'[x]'
to check the checkboxes, or submit the PR and then click the checkboxes)Does this PR already have an issue describing the problem ? If so, link to this issue using
'#XXX'
and skip the rest#46
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API? If yes, check the following:
Other information:
(if any of the questions/checkboxes don't apply, please delete them entirely)