Fix #697 Fix selected graph after create

[Anchel123]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
falkordb-browser	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 5, 2025 9:39am

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[gemini-code-assist]

Hello @Anchel123, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request addresses issue #679, focusing on fixing the selection of graphs after creation. The changes primarily involve modifications to the graph data model and the CreateGraph and Combobox components to ensure proper graph selection and display. Additionally, the GraphDataPanel and SchemaDataPanel components were updated to handle labels, and the GraphView and SchemaView components were modified to manage category visibility and element deletion.

Highlights

• Graph Model Updates: The Graph class in app/api/graph/model.ts was updated to include a displayName property for nodes and links, and to manage categories and labels more effectively. The createCategory method was modified to accept an optional node parameter, and logic was added to associate nodes and links with their respective categories and labels.
• Component Modifications: The CreateGraph component was updated to provide more specific error messages and success notifications. The Combobox component was modified to handle graph selection after creation and deletion. The GraphDataPanel and SchemaDataPanel components were updated to allow adding and removing labels.
• Category Visibility: The GraphView and SchemaView components were updated to manage category visibility by directly manipulating the visible property of elements within a category, and to correctly remove elements from categories upon deletion.

Changelog

Click here to see the changelog

• app/api/graph/model.ts
  • Added displayName property to the Node type.
  • Added elements property to the Category interface.
  • Modified the Graph class to include displayName when creating nodes and links.
  • Added logic to associate nodes and links with their categories and labels.
  • Modified the createCategory method to accept an optional node parameter.
  • Removed the updateCategories method.
  • Added elements property to Category and Label interfaces
• app/components/CreateGraph.tsx
  • Updated error messages to be more specific.
  • Updated success notifications to include the type of graph created.
• app/components/ui/combobox.tsx
  • Removed logic that automatically selected the first option when the options list changed.
  • Modified the delete functionality to correctly update the options list and selected value.
• app/globals.css
  • Updated the background color of the DataPanel and Dropzone classes to use the bg-background utility class.
• app/graph/GraphDataPanel.tsx
  • Added functionality to add and remove labels from nodes.
  • Added state variables and handlers for label editing.
  • Modified the component to display and manage labels using a dynamic list.
• app/graph/GraphView.tsx
  • Modified the onCategoryClick and onLabelClick methods to directly manipulate the visible property of elements within a category or label.
  • Modified the handleDeleteElement method to correctly remove elements from categories and labels.
  • Added handleAddLabel and handleRemoveLabel functions to manage labels on graph nodes.
• app/graph/Selector.tsx
  • Removed the onChange prop and related logic.
  • Modified the handleOnChange method to directly set the graph name.
  • Updated the CreateGraph component to call handleOnChange when a new graph is created.
  • Removed logic that automatically selected the first option when the options list changed.
• app/graph/page.tsx
  • Removed the onChange prop from the Selector component.
• app/schema/SchemaDataPanel.tsx
  • Added functionality to add and remove labels from schema nodes.
  • Added state variables and handlers for label editing.
  • Modified the component to display and manage labels using a dynamic list.
• app/schema/SchemaView.tsx
  • Modified the handleDeleteElement method to correctly remove elements from categories and labels.
  • Added handleAddLabel and handleRemoveLabel functions to manage labels on schema nodes.
• app/schema/page.tsx
  • Modified useEffect dependencies to include session and toast

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

In the realm of graphs, where nodes connect,
A label's touch, a subtle effect.
Adding or removing, a delicate art,
Ensuring the structure remains smart.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request introduces several changes to the graph data model and UI components. The changes include adding a displayName property to the Node type, adding elements to the Category interface, modifying the createCategory function, updating UI components to handle labels, and improving the graph view. Overall, the changes seem to address the issue of selecting the graph after creation and enhance the graph management functionality.

Merge Readiness

The code changes appear to address the issue described in the pull request title. However, due to the lack of specific review comments, I am unable to fully assess the code's correctness and potential impact. I recommend that the author thoroughly test the changes and address any potential issues before merging. I am unable to approve this pull request, and recommend that users have others review and approve this code before merging.