[GH-ISSUE #1994] [Bug] Default single field types incorrectly showing up as un-deletable in Grid #786

New issue

Closed

opened 2026-03-23 20:41:03 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 20:41:03 +00:00

Owner

Originally created by @richardshiue on GitHub (Mar 15, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1994

Originally assigned to: @appflowy on GitHub.

Bug Description

Title says all. Apparently state.isGroupField is true for this field which causes the delete button to become disabled. Though harder to test, this is also observable in the calendar view as well.

How to Reproduce

Create a new grid view
Open a row in this new view as a page
Open the field settings for the "Type" field
See that you can't delete the field

Expected Behavior

It should be deletable unless it really is a grouping field.

Operating System

Fedora Linux 37

AppFlowy Version(s)

0.1.1

Screenshots

Additional Context

No response

Originally created by @richardshiue on GitHub (Mar 15, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/1994 Originally assigned to: @appflowy on GitHub. ### Bug Description Title says all. Apparently `state.isGroupField` is true for this field which causes the delete button to become disabled. Though harder to test, this is also observable in the calendar view as well. ### How to Reproduce 1. Create a new grid view 2. Open a row in this new view as a page 3. Open the field settings for the "Type" field 4. See that you can't delete the field ### Expected Behavior It should be deletable unless it really is a grouping field. ### Operating System Fedora Linux 37 ### AppFlowy Version(s) 0.1.1 ### Screenshots ![image](https://user-images.githubusercontent.com/71320345/225178389-eac4a687-25f4-4fcc-8861-2f89d62754ae.png) ### Additional Context _No response_