parsing submodules seems to be not working

Created on 4 February 2023, almost 2 years ago
Updated 25 May 2024, 6 months ago

Problem/Motivation

And I get messages for the following modules:

Could not parse Composer information for module 'bamboo_twig_config'
Could not parse Composer information for module 'bamboo_twig_extensions'
Could not parse Composer information for module 'bamboo_twig_file'
Could not parse Composer information for module 'bamboo_twig_i18n'
Could not parse Composer information for module 'bamboo_twig_loader'
Could not parse Composer information for module 'bamboo_twig_path'
Could not parse Composer information for module 'bamboo_twig_security'
Could not parse Composer information for module 'bamboo_twig_token'
Could not parse Composer information for module 'computed_field_example_formatter'
Could not parse Composer information for module 'computed_field_php_formatter'
Could not parse Composer information for module 'sophron_guesser'
Could not parse Composer information for module 'tablefield_cellspan'
Could not parse Composer information for module 'tablefield_required'
Could not parse Composer information for module 'views_aggregator_more_functions'

The only common thing I found is they all are located in a sub-folder below the main module.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Closed: cannot reproduce

Version

1.0

Component

Code

Created by

πŸ‡¦πŸ‡ΉAustria maxilein

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @maxilein
  • πŸ‡³πŸ‡±Netherlands ndf Amsterdam

    The only common thing I found is they all are located in a sub-folder below the main module.

    Right now composer installated sub-modules are only found within following directory structure: <MODULE_NAME>/modules/<SUB_MOBULE_NAME>.
    An example that works: web/modules/contrib/PARAGRAPHS/modules/PARAGRAPHS_DEMO for the paragraphs module.

    Can you please share the paths and the way how to install these modules/extensions? That way it can be debugged.

  • πŸ‡¦πŸ‡ΉAustria maxilein

    E.g. the folder structure for
    modules/contrib/bamboo_twig
    modules/contrib/bamboo_twig/bamboo_twig_config/bamboo_twig_config.info.yml
    modules/contrib/bamboo_twig/bamboo_twig_i18n/bamboo_twig_i18n.info.yml
    ..

    I just use composer require ... for each contrib module.
    e.g. composer require drupal/bamboo_twig

    I have no idea how they are installed.
    What are you looking for exactly?

  • πŸ‡³πŸ‡±Netherlands ndf Amsterdam

    I checked the bamboo twig module locally ($ composer require drupal/bamboo_twig), but I cannot reproduce the problem.

    The error you see is triggered here:

    // Remove "drupal/" prefix for Drupal modules, because that breaks
    // the table output in the report.
    if (!str_starts_with($packageName, 'drupal/')) {
      $error_message = "Could not parse Composer information for module '" . $module->getName() . "'";
      throw new UnusedModulesException($error_message);
    }
    

    Do you have anything special with the composer setup? Symlinks or complete git checkout for each modules?

  • First commit to issue fork.
  • Status changed to Closed: cannot reproduce 6 months ago
  • πŸ‡ΊπŸ‡¦Ukraine AstonVictor

    I tested with views_aggregator & computed_field modules and cannot reproduce the issue described in the description. I can see information about both modules and their submodules.

Production build 0.71.5 2024