- Status changed to Fixed
over 1 year ago 11:01am 19 April 2023 - e0ipso Can Picafort
This was discussed in core's MR issue. Re-assigning Project to Drupal core and closing as Fixed.
Automatically closed - issue fixed for 2 weeks with no activity.
To better support external components or components that are defined in files other than *.component.yml it would be great if the discovery system for SDC was pluggable so contrib can provide additional ways to define components outside of *.component.yml files in modules and themes.
My main use case is to have components defined using json as non Drupal frontend developers are usually more familiar with json and json is better supported in other frontend tooling.
Create a new Component Discovery plugin system that is used by the ComponentPluginManager to discover component definitions. The current usage of DirectoryWithMetadataPluginDiscovery would be moved to a YamlDiscovery plugin.
For the ComponentDiscovery plugin definition I'm thinking
/**
* @ComponentDiscovery(
* id="",
* label=@Translation(""),
* plugin_class="",
* weight=0
* )
*/
It'll also be important to make sure the rest of SDC doesn't make any assumptions about where components can come from. Mainly that it doesn't assume components are sourced from a yml file or that component files are necessarily in a module/theme directory.
Fixed
10.1 ✨
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This was discussed in core's MR issue. Re-assigning Project to Drupal core and closing as Fixed.
Automatically closed - issue fixed for 2 weeks with no activity.