All dependencies must be prefixed by project name, So please apply new {project}:{module} format for dephttps://www.drupal.org/docs/8/creating-custom-modules/let-drupal-8-know-... in info.yml filehttps://www.drupal.org/docs/8/creating-custom-modules/let-drupal-8-know-about-your-module-with-an-infoyml-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 Installation profiles to work well. So sooner is better.
Hope this helps.

Comments

chipway created an issue. See original summary.

chipway’s picture

Assigned: chipway » Unassigned
Status: Needs work » Needs review
StatusFileSize
new335 bytes

Here is the patch. Please review.

alonaoneill’s picture

Status: Needs review » Reviewed & tested by the community

Code looks good. The dependency namespacing aligns with Drupal documentation standards.
Patch applied via simplytest.me
Marking as RTBC
Thank you for working on module!

jurriaanroelofs’s picture

Thanks, can you send me a link to the release note or docs for this change? I haven't heard of it before.

  • JurriaanRoelofs committed cf66679 on 8.x-1.x
    Issue #3003425 by chipway, alonaoneill: Dependency namespacing in .info....
jurriaanroelofs’s picture

Status: Reviewed & tested by the community » Fixed

thanks!

volkswagenchick’s picture

According to Drupal standards, modules should include dependencies in the .info.yml file.
Dependencies should be namespaced in the format {project}:{module}, where {project} is the project name as it appears in the Drupal.org URL (e.g. drupal.org/project/views) and {module} is the module's machine name.

https://www.drupal.org/docs/8/creating-custom-modules/let-drupal-8-know-...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.