Skip to content

[Bug] Changing any field in a sorted Grid removes the modified row from proper sort order #7769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rockerest opened this issue Apr 17, 2025 · 1 comment
Assignees

Comments

@rockerest
Copy link

Bug Description

Basically as the title says: If a Grid is sorted, changing any field in a row - even if that field is not part of the sort - removes the row from proper sort order and places it at the bottom of the Grid.

How to Reproduce

  1. Create a Grid
  2. Add some data (at least 2 rows will be necessary to see this in effect)
  3. Add a sort to the Grid
  4. Modify the first row, changing a field that is not part of the applied sort
  5. Note the field is placed at the bottom of the Grid

Expected Behavior

  1. Changing a field should always properly apply the correct sorts and filters
  2. Changing a field that is not part of any sort or filter in the current view should have no effect

Operating System

Windows

AppFlowy Version(s)

0.8.8

Screenshots

Screen.Recording.2025-04-16.202106.mp4

Additional Context

No response

@bogdanpc28
Copy link

I was just going to create the same bug. it's really annoying and it's a basic functionality for a grid that can ruin other features of it if it's not fixed in time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants