What problem would this feature solve?
Component definitions currently support arbitrary metadata through the Metadata type, WithMetadata definition option, and Definition.Metadata method.
There is currently no concrete use case for component metadata in the framework. Keeping this generic mechanism in the public API increases the component definition surface without providing a clear benefit.
It also introduces an untyped extension mechanism that could encourage framework features to rely on arbitrary metadata keys instead of explicit, type-safe APIs.
What would you like to see?
Remove component metadata support from the public component API, including:
- Metadata
- WithMetadata
- Definition.Metadata
- Metadata storage in Definition
Framework features should use dedicated, type-safe definition options or APIs when additional component configuration is required.
What alternatives have you considered?
Keeping metadata as a general-purpose extension mechanism for future framework features.
However, there is currently no concrete requirement for it. Metadata support can be introduced later if a use case emerges that cannot be represented cleanly through a dedicated API.
Additional context
No response
What problem would this feature solve?
Component definitions currently support arbitrary metadata through the Metadata type, WithMetadata definition option, and Definition.Metadata method.
There is currently no concrete use case for component metadata in the framework. Keeping this generic mechanism in the public API increases the component definition surface without providing a clear benefit.
It also introduces an untyped extension mechanism that could encourage framework features to rely on arbitrary metadata keys instead of explicit, type-safe APIs.
What would you like to see?
Remove component metadata support from the public component API, including:
Framework features should use dedicated, type-safe definition options or APIs when additional component configuration is required.
What alternatives have you considered?
Keeping metadata as a general-purpose extension mechanism for future framework features.
However, there is currently no concrete requirement for it. Metadata support can be introduced later if a use case emerges that cannot be represented cleanly through a dedicated API.
Additional context
No response