chore: export node/edge/cell type

[GaoFuhong]

📝 Description

🖼️ Screenshot

Before	After
❌	✅

💡 Motivation and Context

🧩 Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Enhancement (changes that improvement of current feature or performance)
• Refactoring (changes that neither fixes a bug nor adds a feature)
• Test Case (changes that add missing tests or correct existing tests)
• Code style optimization (changes that do not affect the meaning of the code)
• Docs (changes that only update documentation)
• Chore (changes that don't modify src or test files)

🔍 Self Check before Merge

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[gemini-code-assist]

Summary of Changes

Hello @GaoFuhong, 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!

This pull request focuses on improving the discoverability and accessibility of core type definitions within the src/view module. By centralizing the re-export of node, edge, and cell types, it streamlines the development experience for consumers of these types and includes a minor cleanup to remove an unnecessary import.

Highlights

• Type Export Enhancement: The pull request introduces explicit re-exports for cell, edge, and node type definitions from their respective type.ts files via the main src/view/index.ts entry point. This makes these types more readily available for import and usage across the project.
• Code Cleanup: An unused import for CellView was removed from src/view/node/type.ts, contributing to cleaner and more efficient code.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

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

This pull request exports types for nodes, edges, and cells, and also removes an unused import. The changes are functionally correct. I've suggested an alternative approach for exporting the types that could improve modularity by keeping the exports more localized within their respective modules. Please consider this suggestion for better long-term maintainability.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.21%. Comparing base (59380fe) to head (b2bd3cc).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4987   +/-   ##
=======================================
  Coverage   83.21%   83.21%           
=======================================
  Files         334      332    -2     
  Lines       38396    38397    +1     
  Branches     7858     7855    -3     
=======================================
+ Hits        31952    31953    +1     
  Misses       6421     6421           
  Partials       23       23           

Flag	Coverage Δ
x6	83.21% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/view/cell/index.ts	90.39% <100.00%> (+0.01%)	⬆️
src/view/cell/type.ts	100.00% <100.00%> (ø)
src/view/edge/index.ts	59.34% <100.00%> (+0.02%)	⬆️
src/view/node/index.ts	65.05% <100.00%> (+0.03%)	⬆️

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.