However, there are some issues with this mechanism that could be improved. One is that sometimes one feature may depend on another - for example, if the feature required is JQuery Mobile, this also depends on JQuery; however as there is no way to handle this dynamically, the usual solution is to include all dependencies in the feature. However, if the same widget requires multiple features, each of which require the same set of dependencies, then it is very easy for a widget to end up with multiple versions of common includes such as JQuery.
A related issue is versioning - if a widget author has tested their widget using a particular version of a feature, they don't want their widget to fail in deployment if there has been a breaking change in the latest version of the feature dynamically injected by Wookie.
So overall there is a need to make features more robust and predictable for authors and with less duplication of common includes by adding dependencies and versioning to the feature management aspect of Wookie.
|Enable dependencies for features||In Progress||Unassigned|