Epic: Field management

[Acylation]

What would you like to be added?

This issue is started to gathering feature requests related to field management for a more general design.

• Lifting up the field config to the project level.

  • Support adding new fields in the project page #692
  • Provide command / hotkey for new field, correctly pointing active project (fix create note command at the mean time)

• Creating new fields via Table view.

  • Not able to make new fields, change fields, and table collapses when editing a field title. #557
  • Create field through Table view #731
  • In progress improvements:
    • Right-click menu on column header to call the dropdown (In design)
    • In-place rename for column header

• Editing predefined values via Board view.

  • Predefined status values through Board view #482
  • Allow rich-text formatting on board column header #732 Apply richtext to Board column header
  • Board: header overflow, column orders, and clean up column configs #818 implements a sync between predefined value orders and column orders

• Support field configurations (rich-text, options) via all views

  • Show field type icon on view toolbar field picker #891 gives a foundation that field info can be accessed through views

• Better auto suggestions on predefined fields.

  • Epic: Table editing experience #197

• Type casting.

  • Epic: Improve type system #76
  • Manually enforce the data type of a given column #320
  • Can’t change field type #476
  • Can't select other date criteria or use "Check" in Calendar view #582 (derived)
  • Priority sorts incorrectly #704 (derived)

• More detailed column setting of Table view

  • Option to hide column-type icons #484
  • Async field operations (creation, deletion and rename). Update dataframe and project config first, and perform file modifications at the background, need to be tested with a 50+ files project
  • Async file operations (648e86b)
  • Debounced update of Table view upon these operations
  • Duplicate field
  • Add validation upon field rename to avoid unintentional overwriting. Simply ban duplicate field names via Decouple field operations in Table view #817, and will explore merging/overwriting options.

Why is this needed?

Catching up with Obsidian Properties, and provide a more flexible UX.

[Acylation]

List that have complex content types needs to be treated in a clever way.