Skip to content

feat: let a configured project state its bead prefix - #186

Merged
GraemeF merged 1 commit into
mainfrom
lazy-foreign-projects
Sep 29, 2026
Merged

GraemeF merged 1 commit into
mainfrom
lazy-foreign-projects

Conversation

@GraemeF

@GraemeF GraemeF commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

A blocker in a project bdi has not read was reported as possibly in every project not read, because a prefix could only be learned from a tracker's answer. A project entry now takes an optional prefix, and a blocker carrying the prefix one unread project states is reported as held by that project, as held-by-unread in the JSON. A project stating another prefix is no longer listed as a place the blocker may be. A config with no prefix anywhere draws exactly as before.

A blocker in a project bdi has not read was reported as possibly in every project not read, because a prefix could only be learned from a tracker's answer. A project entry now takes an optional `prefix`, and a blocker carrying the prefix one unread project states is reported as held by that project, as `held-by-unread` in the JSON. A project stating another prefix is no longer listed as a place the blocker may be. A config with no `prefix` anywhere draws exactly as before.
@GraemeF
GraemeF merged commit 62a03dc into main Sep 29, 2026
2 checks passed
@GraemeF
GraemeF deleted the lazy-foreign-projects branch September 29, 2026 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant