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-...
Patch to follow, thanks!

CommentFileSizeAuthor
#2 licensing-info-2994141-2.patch246 bytesalonaoneill
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

alonaoneill created an issue. See original summary.

alonaoneill’s picture

alonaoneill CreditAttribution: alonaoneill at Hook 42 commented
Assigned: alonaoneill » Unassigned
Status: Active » Needs review
FileSize
licensing-info-2994141-2.patch246 bytes

I uploaded a patch that corrects the dependency namespacing in the .info.yml file.
Thanks!

volkswagenchick’s picture

volkswagenchick
she/her
Primary language English
Location San Francisco Bay Area
CreditAttribution: volkswagenchick at Hook 42 commented
Status: Needs review » Reviewed & tested by the community

Code looks good. All the projects listed as dependencies on the Extend page for the module are now listed as dependencies. The dependency namespacing aligns with Drupal documentation standards.

Patch applied via simplytest.me

Marking as RTBC

grasmash’s picture

grasmash CreditAttribution: grasmash at Acquia commented
Status: Reviewed & tested by the community » Fixed

  • grasmash committed a12d8ab on 8.x-1.x authored by alonaoneill 
    Issue #2994141 by alonaoneill: Dependency namespacing in .info.yml file

Status: Fixed » Closed (fixed)

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