Misc Collection Enhancements

[weilies]

1. Support "Password" field from collection > schema > new field

Background:

• User unable to add masked field (e.g. password/secret) into collection's field

Expectation:

• Add a "Password" field under "Field Type" dropdown (1) OR extend Field Type "Text", to have a flag "Masked"/ "Is Password" (3) or equalvalent
• Once the field is "Password" type, the RAW value mustn't be log in audit (recommend market practice, store as "" or "" or "****")
• Value also must not retrievable in Query Generator/Supabase

2. Navigation should be collapse / expand

Expectation: * menu collapse / expand / expand-when-mouse-over (reference MS Excel top menu item bar)

3. Collection > Layout refinement

Background:

• I vibe-coded using Haiku model, extended with "Parent Record Layout", (2) in screenshot below and the UX different from "Detail Form Layout" (1)

Expectation:

• (3) - user gotto define number 1/2/3 to determine the space occupied when render on screen (e.g. 1/1/1 means 3 items in a row). Please refer notion's column widget or here, in the "Add Element" drawer (5), could we add two options like "2 columns", "3 columns", then for each field dragged into the Layout model, the system automatically knows how the field is possition? Like into first/second/third column
• (6), (7) - both detail form and parent record show different way to re-order field sequence. Best is user can drag-drop reorder the fields. As smooth as notion (i might be over demand lol)
• (1), (2) - rework on both parent/detail's Layout. Make them adopt similar UX to order the display of fields to frontend
• (4) Parent Record layout doesn't hv "Add Element" and it should be same as detail layout

4. Form Layout miss-aligned when view as "Parent" (Edit > Prompt, (2) below)

Background

• When "Employees" collection's item is viewed (with child collection attached to them below), user hit "Edit" (7) and dialogbox prompted (2). Everything in field is reflect top-down. Expecting to render as per Layout defined (1)

Expectation:

• User defined 2 columns to show Employees's fields, it's reflect as per configuration (Add Item (4) > Add Item dialogbox (1) prompted > fields displayed as 2 columns). When same collection viewed as parent > "Edit" clicked (7), the prompted form must respect layout
• Make this enhancement apply across System Collection/Tenant Collection (5), as well as they are under "Collection" section (6)

5. Navigation Enhancement

Background:

• Misc UX enhancement required when Studio > Navigation (1) clicked

Expectation:

• (2) align the ">" (expand icon), default all folders are "collapse-by-default"
• (4) make "Folder" icon is default, but can be override with lucide icon
• (3) resolve the move up/down icon. I noticed sometime the "move up" doesn't really move the current folder above/below. Also ensure moving up/down will stay within current folder level. Moving it up never means to be under the child of the folder placed above.
• (6) when holding the folder/item, user is allow to move to any folder in any level. a non-folder item dragging can always move into another folder, but it can't move into another non-folder item (e.g. an "Employees" collection can't move into another "Contact" collection)
• (5) display folder-id when mouse over the folder
• Ensure non-super tenant user if they are granted access to this screen, they can't add/remove folder at this moment. In future (roadmap) when tenant is given access to expand via app, they are allow to assign new screen/form under the designation folder (via folder id). Hence these folder can't be edit by them

[weilies]

Item 1, 2, 3, 4 resolved.
item 5 still error. To be resolve in future release