Skip to content
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

✨ Grouping TableNodes without Relationships into a GroupNode and Applying a New Layout Definition #322

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

junkisai
Copy link
Member

@junkisai junkisai commented Dec 19, 2024

Summary

I have grouped TableNodes without Relationships into a GroupNode, allowing a new layout definition to be applied.
The new layout definition arranges the Nodes in a single vertical column.

Before After
スクリーンショット 2024-12-19 17 36 17 スクリーンショット 2024-12-19 17 35 54

@junkisai junkisai changed the title Feat/group nodes ✨ Grouping TableNodes without Relationships into a GroupNode and Applying a New Layout Definition Dec 19, 2024
Comment on lines +30 to +33
const tableNodesInitialized = nodes
.filter((node) => node.type === 'table')
.some((node) => node.measured)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before adding the Group Node, nodesInitialized would become true only when the drawing occurred after the conversion to TableNode was completed by convertDBStructureToNodes().

However, with the addition of the Group Node, nodesInitialized started to become true even before the conversion to TableNode was completed. As a result, we created our own custom nodesInitialized.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that makes sense!

@junkisai junkisai marked this pull request as ready for review December 19, 2024 08:54
@junkisai junkisai requested a review from a team as a code owner December 19, 2024 08:54
@junkisai junkisai requested review from hoshinotsuyoshi, FunamaYukina, MH4GF and sasamuku and removed request for a team December 19, 2024 08:54
Copy link
Member

@hoshinotsuyoshi hoshinotsuyoshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work! 🎉

Now, could you confirm if selecting All Fields hides all nodes? 👀

@MH4GF
Copy link
Member

MH4GF commented Dec 19, 2024

The All Fields display seems to be corrupted. Please check this problem? @junkisai

スクリーンショット 2024-12-19 19 20 02

Copy link
Member

@MH4GF MH4GF left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation looked good!
This is great work! 😄

Comment on lines +30 to +33
const tableNodesInitialized = nodes
.filter((node) => node.type === 'table')
.some((node) => node.measured)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that makes sense!

@junkisai
Copy link
Member Author

@MH4GF @hoshinotsuyoshi

The All Fields display seems to be corrupted. Please check this problem?

I didn't notice until you pointed it out...
I'll check on it!

@junkisai junkisai marked this pull request as draft December 19, 2024 12:07
@MH4GF
Copy link
Member

MH4GF commented Dec 19, 2024

@junkisai
I know it's a difficult problem, but thank you in advance 🙏🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants