[PR #4791] [MERGED] fix: reorder field updating all views #6443

Closed
opened 2026-03-23 22:23:14 +00:00 by mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AppFlowy-IO/AppFlowy/pull/4791
Author: @richardshiue
Created: 3/1/2024
Status: Merged
Merged: 3/2/2024
Merged by: @richardshiue

Base: mainHead: fix/move-field


📝 Commits (1)

  • 3be71ac fix: reorder field updating all views

📊 Changes

1 file changed (+4 additions, -2 deletions)

View changed files

📝 frontend/rust-lib/flowy-database2/src/services/database/database_editor.rs (+4 -2)

📄 Description

resolves https://github.com/AppFlowy-IO/AppFlowy/pull/4791

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/4791 **Author:** [@richardshiue](https://github.com/richardshiue) **Created:** 3/1/2024 **Status:** ✅ Merged **Merged:** 3/2/2024 **Merged by:** [@richardshiue](https://github.com/richardshiue) **Base:** `main` ← **Head:** `fix/move-field` --- ### 📝 Commits (1) - [`3be71ac`](https://github.com/AppFlowy-IO/AppFlowy/commit/3be71ac38325c4eb7333b3e888cb0f4e3d4bf131) fix: reorder field updating all views ### 📊 Changes **1 file changed** (+4 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `frontend/rust-lib/flowy-database2/src/services/database/database_editor.rs` (+4 -2) </details> ### 📄 Description resolves https://github.com/AppFlowy-IO/AppFlowy/pull/4791 ### 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 22:23:14 +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#6443
No description provided.