Community
Participate
Working Groups
(I have not had a chance to confirm this, but based on the spec it suggests this is the case) If a feature does not have an associated plugin, then this implies that another feature cannot include or require it since include/require is based on the plugin id of the feature's plugin according to the spec. If this is supported the spec/doc on the update component web page should be clarified & this can be downgraded to a p3. Peter M. may have had an opportunity to test this out for sure. Apologies that I have not had a chance to confirm spec theory.
Hum , we may not be clear. I can see the includes tag seems to require a feature id, but the requires tag needs a plugin id. We should make it clearer that include is for feature nesting, while requires is for plugin dependency. So, in a nutshell, you should be able, in the current spec, to include a feature that doesn't have a plugin. the require tag takes a plugin id and is not used for nesting... Move to p3 as specified, change spec
Investigate if it is doable to add an attribute 'feature' in the 'import' element in requires to allow feature prereq instead of plug-in prereq.
Attribute feature has been added. test
Core is now supporting 'feature' in 'import' elements, Update UI modified to handle it.
Implemented - needs testing.
Fixed.
