- Issue created by @AlMunnings
- πΊπΈUnited States cmlara
Linking related proposal that would prevent this from being an ongoing issue π± Change how modules and submodule dependencies are handled to have more consistent namepsaces [DRAFT]. Active
- πΊπΈUnited States drumm NY, US
This is by design to prevent a new module from overriding a component of another project. In some cases, it is possible to get the package names reset. In the meantime,
drupal/graphql_compose_fragments-graphql_compose_fragments
is correct, Compose package names do not always match project names. - π¦πΊAustralia AlMunnings Melbourne
Considering that I am the author of both modules, perhaps it could be taken into consideration:
- the meta package didn't work as desired
- there was no stable release including the sub module
- the sub module no longer existsAnd now itβs causing unwanted side effects.
Is it possible to remove the meta package? Or rename it to free up the normal package name?
π
- Status changed to Needs review
24 days ago 1:10pm 1 June 2024