kindred/create
1
1
Fork 0
Code Issues 53 Pull Requests Actions Packages Projects 9 Releases 2 Wiki Activity

bug(silo): Silo_BOM requires Silo-tracked document with no registration path #56

New Issue
Closed
opened 2026-02-08 23:25:54 +00:00 by forbes · 0 comments
forbes commented 2026-02-08 23:25:54 +00:00
Owner
Copy Link

The Silo_BOM command depends on the SiloPartNumber property. When used on an unregistered document, it shows a warning but provides no path to register the document with Silo.

Expected: Either allow BOM on unregistered documents or provide a registration flow from the warning dialog.

Priority: Medium
Source: KNOWN_ISSUES.md #7

The `Silo_BOM` command depends on the `SiloPartNumber` property. When used on an unregistered document, it shows a warning but provides no path to register the document with Silo. **Expected:** Either allow BOM on unregistered documents or provide a registration flow from the warning dialog. **Priority:** Medium **Source:** KNOWN_ISSUES.md #7
forbes added the bugUX labels 2026-02-08 23:25:54 +00:00
forbes referenced this issue from a commit 2026-02-14 16:31:28 +00:00
Fix #56 ViewSection
forbes referenced this issue from a commit 2026-02-14 16:34:32 +00:00
Fix #56 ViewSection
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
UX
branding
bug
ci/cd
CI/CD workflows and deployment
 defaults
documentation
Developer documentation
 enhancement
high-priority
low-priority
theme
No Label UX bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
forbes
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kindred/create#56
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?