All dependencies must be prefixed by project name, So please apply new {project}:{module} format for dependencies in info.yml file
It is supported since 8.0 and 7.40 Change Record: Project namespaces can now be added for module dependencies, and is now a Best Practice Define project dependencies in core module .info files).
It is useful for DrupalCi to download the right dependencies and Installation profiles to work well. So sooner is better.
Hope this helps.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | Update_dependencies_format_in_info.yml_3011936-2.patch | 383 bytes | chipway |
Comments
Comment #2
chipway commentedHere is the patch. Please review.
Comment #3
geerlingguy commentedLooks okay to me, I think... but I want to know more about why this strange new format seems to be preferred; I asked in #2798891-24: Define project dependencies in core module .info files, but do you have any more insight into why this is being changed? And more specifically, why Drupal is using a weird format for the dependency definition which differs from Composer?
Comment #4
mlncn commentedThis was included as part of #3129608: Drupal 9 readiness and code standarts
Thank you chipway!
And i'm still not entirely clear on the format change but presumably it will help prevent namespace conflicts with submodules at some point? These are prefixed with drupal because they are drupal core; submodules have modulename:submodulename syntax. But yeah not clear on practical benefits either.