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

Expand duplicate plan to cover all entity types; clarify bins need fields too

Browse Source 
- Generalized 'Duplicate bin type' to 'Duplicate any entity' covering
  components, bins, bin types, grids, templates, inventory, source images
- Clarified that bins (not just bin types) should carry generic fields

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
mikael-lovqvists-claude-agent
2026-04-03 03:25:22 +00:00
parent b0eaf4dc10
commit 5e2a348b9d
1 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
future-plans.md
View File

@@ -424,7 +424,7 @@ This also enables filtering/grouping bins by type, and makes it easy to re-proce
all bins of a type if the corner algorithm improves. all bins of a type if the corner algorithm improves.
### Generic fields on bins and bin types ### Generic fields on bins and bin types
Bins and bin types should support the same generic field system as components — Bins and bin types should both support the same generic field system as components —
arbitrary key/value pairs from the shared field definitions. Examples: color, material, arbitrary key/value pairs from the shared field definitions. Examples: color, material,
manufacturer, max load, purchase link. Bin types carry the "template" fields (e.g. manufacturer, max load, purchase link. Bin types carry the "template" fields (e.g.
nominal dimensions from the datasheet) while individual bins carry instance-specific nominal dimensions from the datasheet) while individual bins carry instance-specific
@@ -435,10 +435,14 @@ the system, they will quickly span unrelated domains. Field grouping (see Field
section) becomes important here so the field selector can be filtered to show only section) becomes important here so the field selector can be filtered to show only
relevant fields for the current entity type. relevant fields for the current entity type.
### Duplicate bin type ### Duplicate any entity
Bin types should be duplicatable — common when you have the same physical container All objects in the system should be duplicatable: components, bin types, bins, grids,
in different colors, sizes, or configurations. Duplicating copies all fields and templates, inventory entries, and eventually source images. The duplicate operation
dimensions; the user then adjusts what differs. creates a new record with all fields copied, then opens it in an edit dialog so the
user can adjust what differs. Bin type duplication is especially common — same
physical container model in different colors or configurations. Source images are a
later case since they reference uploaded files; duplication there would mean creating
a new metadata record pointing to the same underlying file (or an explicit copy).
## Grids ## Grids