- Issue created by @jurriaanroelofs
- πΊπΈUnited States cmlara
See π± Change how modules and submodule dependencies are handled to have more consistent namepsaces [DRAFT]. Active for the long story on this and how sub modules can steal composer namespaces (and related proposal to prevent this from occurring)
See π¬ Submodule created a package Active where a similar request was most recently rejected.
$ composer show -a drupal/analyze_ai_sentiment name : drupal/analyze_ai_sentiment descrip. : A submodule for Analyze that provides AI-powered sentiment analysis capabilities. keywords : versions : 1.0.x-dev, dev-1.0.x type : metapackage license : GNU General Public License v2.0 or later (GPL-2.0-or-later) (OSI approved) https://spdx.org/licenses/GPL-2.0-or-later.html#licenseText homepage : https://www.drupal.org/project/analyze source : [] dist : [] names : drupal/analyze_ai_sentiment support source : https://git.drupalcode.org/project/analyze
Infra has the final say, however I would suggest (based on prior actions) you be prepared to consider either being stuck with the duplicate name, or consider abandoning the namespace to choose a new (non-duplicated) name.
- π³π±Netherlands jurriaanroelofs
Thanks for the quick update. I hope we can get the name deduplicated, I've already had developers spend hours in confusion over the "wrong" module path causing bugs so I will prepare to move into a new namespace if infra's policy is not to help change this, no big deal.
- πΊπΈUnited States drumm NY, US
This is by design, not a bug, and a rename can be considered on a case-by-case basis. The composer namespace does not always match the project name.
- π³π±Netherlands jurriaanroelofs
ok thx for the update, I will create a new project