[PR #5753] [CLOSED] feat: show optimize space button if detecting page missing #6991

Closed
opened 2026-03-23 23:17:36 +00:00 by mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AppFlowy-IO/AppFlowy/pull/5753
Author: @LucasXu0
Created: 7/17/2024
Status: Closed

Base: mainHead: optimize_space


📝 Commits (3)

  • 38c3633 feat: show optimize space button if detecting page missing
  • 49e2e3a chore: update frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/space/shared_widget.dart
  • bdcb373 fix: compile

📊 Changes

8 files changed (+308 additions, -157 deletions)

View changed files

📝 frontend/appflowy_flutter/lib/workspace/application/menu/sidebar_sections_bloc.dart (+4 -0)
📝 frontend/appflowy_flutter/lib/workspace/application/sidebar/space/space_bloc.dart (+12 -3)
📝 frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/sidebar.dart (+4 -1)
📝 frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/space/shared_widget.dart (+180 -0)
📝 frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/space/space_migration.dart (+12 -152)
frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/space/space_optimization.dart (+36 -0)
📝 frontend/appflowy_flutter/lib/workspace/presentation/settings/pages/fix_data_widget.dart (+56 -0)
📝 frontend/resources/translations/en.json (+4 -1)

📄 Description

Feature Preview


PR Checklist

  • My code adheres to AppFlowy's Conventions
  • I've listed at least one issue that this PR fixes in the description above.
  • I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
  • All existing tests are passing.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/AppFlowy-IO/AppFlowy/pull/5753 **Author:** [@LucasXu0](https://github.com/LucasXu0) **Created:** 7/17/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `optimize_space` --- ### 📝 Commits (3) - [`38c3633`](https://github.com/AppFlowy-IO/AppFlowy/commit/38c3633428d06180b492775b843427f075715383) feat: show optimize space button if detecting page missing - [`49e2e3a`](https://github.com/AppFlowy-IO/AppFlowy/commit/49e2e3a223c53524d1fafb7e5c7b584074145aa1) chore: update frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/space/shared_widget.dart - [`bdcb373`](https://github.com/AppFlowy-IO/AppFlowy/commit/bdcb373654f6f1ff80a7d9fa1f9a1d29d65b3f85) fix: compile ### 📊 Changes **8 files changed** (+308 additions, -157 deletions) <details> <summary>View changed files</summary> 📝 `frontend/appflowy_flutter/lib/workspace/application/menu/sidebar_sections_bloc.dart` (+4 -0) 📝 `frontend/appflowy_flutter/lib/workspace/application/sidebar/space/space_bloc.dart` (+12 -3) 📝 `frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/sidebar.dart` (+4 -1) 📝 `frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/space/shared_widget.dart` (+180 -0) 📝 `frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/space/space_migration.dart` (+12 -152) ➕ `frontend/appflowy_flutter/lib/workspace/presentation/home/menu/sidebar/space/space_optimization.dart` (+36 -0) 📝 `frontend/appflowy_flutter/lib/workspace/presentation/settings/pages/fix_data_widget.dart` (+56 -0) 📝 `frontend/resources/translations/en.json` (+4 -1) </details> ### 📄 Description <!--- Thank you for submitting a pull request to AppFlowy. The team will dedicate their best efforts to reviewing and approving your pull request. If you have any questions about the project or feedback for us, please join our [Discord](https://discord.gg/wdjWUXXhtw). --> <!--- If your pull request adds a new feature, please drag and drop a video into this section to showcase what you've done! If not, you may delete this section. --> ### Feature Preview <!--- List at least one issue here that this PR addresses. If it fixes the issue, please use the [fixes](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests) keyword to close the issue. For example: fixes https://github.com/AppFlowy-IO/AppFlowy/pull/2106 --> --- <!--- Before you mark this PR ready for review, run through this checklist! --> #### PR Checklist - [ ] My code adheres to [AppFlowy's Conventions](https://docs.appflowy.io/docs/documentation/software-contributions/conventions) - [ ] I've listed at least one issue that this PR fixes in the description above. - [ ] I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes. - [ ] All existing tests are passing. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
mirror 2026-03-23 23:17:36 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#6991
No description provided.