Skip to content

Supersede plugin tuples with options like plain specs - #133

Merged
trick77 merged 1 commit into
masterfrom
worktree-plugin-tuple-supersede
Oct 4, 2026
Merged

trick77 merged 1 commit into
masterfrom
worktree-plugin-tuple-supersede

Conversation

@trick77

@trick77 trick77 commented Oct 4, 2026

Copy link
Copy Markdown
Owner

opencode accepts [name@spec, {options}] entries in plugin. specName only recognised plain strings, so switching between a preset that passes plugin options and one that does not left both entries and loaded the plugin twice. Tuples now count as the same package in both directions.

Needed for a planify preset that passes a Bitbucket URL and token as plugin options.

opencode accepts [name@spec, {options}] in plugin. specName ignored
that shape, so switching between a preset with plugin options and one
without left the plugin loaded twice.
@trick77
trick77 merged commit fe0aaf3 into master Oct 4, 2026
3 checks passed
@trick77
trick77 deleted the worktree-plugin-tuple-supersede branch October 4, 2026 15:36
trick77 added a commit that referenced this pull request Oct 4, 2026
Master carries two changes since v0.28.0: plugin entries written as
[name@spec, {options}] now supersede a plain spec of the same package
(#133), and opencode-planify-german moves to 0.4.0 with plan_pr, whose
plugin preset prompts for a Bitbucket URL and token (#134). Both are
features, so this is a minor.
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