mikael-lovqvists-claude-agent/electronics-inventory
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

future-plans: type field approach for item types, bulk migration strategy

Browse Source 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
mikael-lovqvists-claude-agent
2026-04-01 03:38:02 +00:00
parent e83d3978b0
commit 80a2fabf7d
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
future-plans.md
View File

@@ -356,8 +356,13 @@ multiple item types (components, bins, tools, materials, etc.) with:
- The current components section becomes one such type-specific view rather than - The current components section becomes one such type-specific view rather than
the only view the only view
This is a significant architectural change — not needed now, but should inform data **Implementation approach:** Add a `type` field to items (e.g. `component`, `bin`,
model decisions so we don't paint ourselves into a corner. `tool`). Type-specific views are just filtered views over all items. No separate
collection or schema per type — the type field drives which view renders it.
**Migration:** Bulk assignment via the existing field system — e.g. set `type =
"component"` on all current items in one operation, since they're all components.
No per-item manual work needed.
### Inventory URL reflects selected entry ### Inventory URL reflects selected entry
Similar to how components now reflect `/components/:id` in the URL, inventory Similar to how components now reflect `/components/:id` in the URL, inventory