F-070: revise plugins design (static register / custom type)#185
Merged
Conversation
added 2 commits
July 19, 2026 09:54
Reject free-form plugins= lists on every target. Plugin identity lives on static registration (pre-defined types) or custom target types; instances only take optional uniform pluginConfig.
Call sites are attributes-only. Extending a target type with a plugin applies it on every use. Reject per-callsite pluginConfig(binding).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Corrects F-070 after product feedback: do not put free-form
plugins = plugins(plugin(\"id\")…)on every target.Correct model
registerTargetPluginpluginConfigpluginConfigDeprecate chain
withPlugin/PluginWrapper. Catalog KSP + FeatureDefinition unchanged.Full rewrite:
docs/TARGET-PLUGINS.md. TICKETS F-071–F-073 notes aligned.Test plan