Remove Atlas2 RepulsionFromFixedNodes parameter#793
Merged
Conversation
Signed-off-by: Nathan Dissoubray <nathan.dissoubray@rte-france.com>
Signed-off-by: Nathan Dissoubray <nathan.dissoubray@rte-france.com>
|
flo-dup
approved these changes
Mar 9, 2026
github-project-automation
Bot
moved this from Waiting for review
to Approved
in Release 03/2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Remove the RepulsionForceFromFixedNodes parameter in Atlas2, as it is not really useful.
What is the current behavior?
The parameter currently exists.
What is the new behavior (if this is a feature change)?
Now it doesn't.
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information:
This is not a breaking change as Atlas2 was introduced by #721 which is for March release, so the parameter was not in a released version of diagram yet.