Skip to content

README: mvvm.Queue needs go-widgets/mvvm v0.14.0 or later - #144

Merged
tannevaled merged 1 commit into
mainfrom
readme-queue-version
Oct 11, 2026
Merged

tannevaled merged 1 commit into
mainfrom
readme-queue-version

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

The Results from other goroutines section (#140) tells an application to post to an mvvm.Queue. Queue arrived in go-widgets/mvvm v0.14.0, and this module builds against mvvm v0.9.0 (via toolkit). So an application that copies the example gets a build error unless its own go.mod requires mvvm ≥ v0.14.0. The README now says so.

Found by docsym, a new go-fleettools command. It type-checks the names a README cites, at the version the module actually builds against. The <!-- docsym:allow … -- reason --> comment (renders as nothing) records why this mention is correct, so the tool stops reporting it; it ignores an allow with no reason.

README only.

🤖 Generated with Claude Code

The README tells an application to post results to an mvvm.Queue. Queue
arrived in mvvm v0.14.0, and this module builds against v0.9.0 (through
toolkit), so an application copying the example needs mvvm at v0.14.0 or above
in its own go.mod; the README now says so. Found by docsym
(go-fleettools/fleettools), which looks names up at the version a module
actually builds against; the docsym:allow comment records why this one is right.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tannevaled
tannevaled force-pushed the readme-queue-version branch from 1f3a4ca to 52e91b2 Compare October 11, 2026 17:27
@tannevaled
tannevaled merged commit 87b7f44 into main Oct 11, 2026
28 checks passed
@tannevaled
tannevaled deleted the readme-queue-version branch October 11, 2026 17:30
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