Talon/chat_grid
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: complete server-first item schema wiring and plugin contract checks

Browse Source
This commit is contained in:
Jage9
2026-02-24 18:48:08 -05:00
parent 7776676e2d
commit fcb5e85b13
20 changed files with 132 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
plans/item-architecture-refactor-plan.md
View File

@@ -338,7 +338,7 @@ Implementation:
- Keep compile-time unions only where they materially improve safety and can be generated/centralized.
Acceptance criteria:
- Adding a new item plugin does not require editing multiple type-literal lists in unrelated files.
- New type appears in add/edit flows after server metadata update with minimal client changes (or none for generic items).
- New type appears in add/edit flows after server metadata update with minimal client changes.
3. **Include `capabilities` in `welcome.uiDefinitions.itemTypes` (medium).**
Scope:
@@ -360,8 +360,7 @@ Problem today:
Implementation:
- Server emits list options at `propertyMetadata[key].options`.
- Client reads options from metadata first.
- Deprecate/remove separate `propertyOptions` map after migration.
- Keep transition shim only during one deploy window if needed.
- Remove separate `propertyOptions` map.
Acceptance criteria:
- One canonical place (`propertyMetadata`) defines type, range, tooltip, options, and visibility for each property.
- New list property requires server-only metadata changes for options.