Update nad-viewer following powsybl-diagram v4.6.0 release #110
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
…gram (#92) Signed-off-by: Massimo Ferraro <massimo.ferraro@soft.it>
Signed-off-by: Massimo Ferraro <massimo.ferraro@soft.it>
flo-dup
force-pushed
the
integration/nad_4.6.0
branch
from
efd3feb to
a54ec44
Compare
|
massimo-ferraro
approved these changes
Nov 4, 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?
Update powsybl-diagram to v4.6.0 (metadata changes)
What is the current behavior?
moving nodes in nad-viewer works only with svgs from powsybl-diagram <v4.6.0
What is the new behavior (if this is a feature change)?
moving nodes in nad-viewer works onlywith svgs from powsybl-diagram >=v4.6.0
Does this PR introduce a breaking change or deprecate an API?