docs: backlog — allow renaming group IDs with cascaded reference updates
This commit is contained in:
@@ -22,7 +22,12 @@ When creating a unit or group, allow the user to optionally supply their own ID.
|
|||||||
- If the user types into the ID field, stop auto-generating and use what they typed.
|
- If the user types into the ID field, stop auto-generating and use what they typed.
|
||||||
- Validate: IDs must be unique and slug-safe.
|
- Validate: IDs must be unique and slug-safe.
|
||||||
|
|
||||||
### Admin: "Delete" action in the bulk actions menu
|
### Admin: allow renaming group IDs
|
||||||
|
The group edit form currently does not expose the `id` field. Since storage is a flat
|
||||||
|
JSON file, renaming a group ID is straightforward: update `groups[].id` and rewrite
|
||||||
|
every `units[].group` reference in the same atomic save. Should also validate the new
|
||||||
|
ID is unique and kebab-safe before committing.
|
||||||
|
|
||||||
Add a "Delete" option to the bulk action dropdown so multiple units can be deleted at
|
Add a "Delete" option to the bulk action dropdown so multiple units can be deleted at
|
||||||
once. Should show a confirmation dialog listing the units to be deleted before
|
once. Should show a confirmation dialog listing the units to be deleted before
|
||||||
committing. Related to the immediate fix below (ungrouped bulk actions).
|
committing. Related to the immediate fix below (ungrouped bulk actions).
|
||||||
|
|||||||
Reference in New Issue
Block a user