chore(editor): remove Audio and Gantt extensions

[xun082]

PR 描述

PR 类型

• 🐛 Bug 修复
• ✨ 新功能
• 💄 UI/UX 改进
• ♻️ 重构
• 🚀 性能优化
• 📝 文档更新
• 🔄 其他

Issue 关联

Closes #

其他信息

[netlify]

❌ Deploy Preview for ornate-blancmange-89db6b failed. Why did it fail? →

Name	Link
🔨 Latest commit	cbef62d
🔍 Latest deploy log	https://app.netlify.com/projects/ornate-blancmange-89db6b/deploys/698b32df296f4e0008b2073e

[gemini-code-assist]

Summary of Changes

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

此拉取请求主要旨在通过删除不再需要的音频和甘特图编辑器扩展来优化和清理项目。同时，它还改进了房间页面的加载体验，通过引入 Suspense 边界和回退 UI，确保用户在内容加载时能看到友好的提示。

Highlights

• 移除音频和甘特图扩展: 此拉取请求移除了编辑器中不再使用的音频（Audio）和甘特图（Gantt）扩展及其所有相关文件和引用，以精简代码库并减少不必要的依赖。
• 房间页面加载优化: 为 apps/DocFlow/src/app/rooms/page.tsx 文件添加了 Suspense 和 RoomsPageFallback 组件，以在页面内容加载时提供更好的用户体验。

Changelog

• apps/DocFlow/src/app/rooms/page.tsx
  • 导入了 Suspense 组件
  • 将原有的默认导出 Page 组件重命名为 RoomsPageContent
  • 新增了 RoomsPageFallback 组件，用于显示加载中的UI
  • 更新了默认导出的 Page 组件，使用 Suspense 包裹 RoomsPageContent 并指定 RoomsPageFallback
• apps/DocFlow/src/extensions/Audio/Audio.ts
  • 移除了音频 Tiptap 节点扩展的定义文件
• apps/DocFlow/src/extensions/Audio/AudioComponent.tsx
  • 移除了用于渲染音频节点的 React 组件文件
• apps/DocFlow/src/extensions/Audio/index.ts
  • 移除了音频扩展的导出文件
• apps/DocFlow/src/extensions/Gantt/Gantt.ts
  • 移除了甘特图 Tiptap 节点扩展的定义文件
• apps/DocFlow/src/extensions/Gantt/GanttComponent.tsx
  • 移除了用于渲染甘特图的 React 组件文件
• apps/DocFlow/src/extensions/Gantt/components/GanttTaskDialog.tsx
  • 移除了甘特图任务管理对话框组件文件
• apps/DocFlow/src/extensions/Gantt/components/index.ts
  • 移除了甘特图组件的导出文件
• apps/DocFlow/src/extensions/Gantt/index.ts
  • 移除了甘特图扩展的导出文件
• apps/DocFlow/src/extensions/SlashCommand/groups.ts
  • 从斜杠命令组中移除了对 'audio' 命令的引用
  • 从斜杠命令组中移除了对 'gantt' 命令的引用
• apps/DocFlow/src/extensions/extension-kit.ts
  • 移除了对 Audio 扩展的导入和使用
  • 移除了对 Gantt 扩展的导入和使用
• apps/DocFlow/src/extensions/index.ts
  • 移除了对 Audio 扩展的导出
  • 移除了对 Gantt 扩展的导出
• apps/DocFlow/src/utils/editor/is-custom-node-selected.ts
  • 从自定义节点选择工具函数中移除了对 Audio 扩展的引用

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

这个 PR 主要做了两件事：首先，它移除了不再需要的 Audio 和 Gantt 编辑器扩展，相关的代码文件和引用都已经被干净地清除了。其次，在 rooms 页面引入了 React.Suspense，这是一个很好的实践，通过为使用 useSearchParams 的客户端组件提供一个 Fallback UI，优化了页面的加载体验。整体来看，代码变更清晰、正确，没有发现问题。做得很好！