-
Notifications
You must be signed in to change notification settings - Fork 33
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
refactor: [POC] Replace mxGraph with maxGraph 0.1.0 #2366
Closed
Closed
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
- Replace mxCellState by CellState - Replace mxCellRenderer by CellRenderer - Replace mxCellOverlay by CellOverlay
csouchet
added
WIP 🚧
Pull request in progress and/or not ready for review. Used in addition to marking it as draft
poc 💫
Experimentation to discuss about future implementation. Not intended to be merged
labels
Nov 23, 2022
csouchet
changed the title
[POC] Bump maxgraph to 0.1.0
[POC] Replace mxgraph with maxgraph 0.1.0
Nov 23, 2022
csouchet
force-pushed
the
poc/bump_maxgraph_0.1.0
branch
from
November 24, 2022 10:10
d6dbba5
to
7da1141
Compare
- Replace mxSvgCanvas2D.format:(value: string) => number by SvgCanvas2D.format:(value: number) => number
This was referenced Feb 26, 2023
This is too early, we will do it if we actually migrate to maxGraph
This reverts commit cfc224a
…the code We only want to see the technical impacts of the migration to maxGraph here
We only want to see the technical impacts of the migration to maxGraph here Comment will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment will be updated while or after doing the actual migration This reverts commit 7b1d761
We only want to see the technical impacts of the migration to maxGraph here Comment will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment/variables will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment/variables will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment/variables will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment/variables will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment/variables will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment/variables will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment/variables will be updated while or after doing the actual migration
We only want to see the technical impacts of the migration to maxGraph here Comment/variables will be updated while or after doing the actual migration
tbouffard
reviewed
Jun 7, 2023
This was referenced Jun 13, 2023
tbouffard
added
mxgraph integration
Something involving mxGraph (be aware of EOL)
and removed
WIP 🚧
Pull request in progress and/or not ready for review. Used in addition to marking it as draft
labels
Jul 4, 2023
POC completed, a new one has just started in #2756. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
mxgraph integration
Something involving mxGraph (be aware of EOL)
poc 💫
Experimentation to discuss about future implementation. Not intended to be merged
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.
This is a POC and it is not intended to be merged into master, so don't expect to find a high quality code here! 😺
Please don't rebase on
master
. We don't need it as we just want to evaluate the migration.Purpose
Gains
Detected issues in
maxGraph
Styles
labelPosition
property to restore "no align" maxGraph/maxGraph#203Types
Others
mxToolip
element created in the DOM after the element holding the graph: Extra mxToolip elements created in the DOM maxGraph/maxGraph#200