Fix DanglingLine ID in Eurostag example network with tie-lines #3154
+19
−19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Damien Jeandemange <damien.jeandemange@artelys.com>
jeandemanged
force-pushed
the
fix-eurostag-tutorial-ex1-danglingline-id-typo
branch
from
59debe5
to
988ca38
Compare
annetill
approved these changes
Sep 25, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No
What kind of change does this PR introduce?
Quality
What is the current behavior?
Confusing NVH1_XNODE2 dangling line ID for dangling line between NHV1 and Xnode XNODE2.
(The other dangling line NHV1_XNODE1 is ok.)
What is the new behavior (if this is a feature change)?
NVH1_XNODE2 renamed NHV1_XNODE2
Does this PR introduce a breaking change or deprecate an API?