You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
When requiring openeuropa/oe_list_pages which requires drupal/emr we are facing an issue which is a wrong entry in composer autoload_psr4 which is pointing to root src/ directory instead of the relative path to the contrib module.
'Drupal\\emr\\' => array($baseDir . '/src'),
And this is impacting in case of having custom classes for the project under root src/ directory.
When individually requiring drupal/entity_meta_relation 1.2.0 what you get in lock file is not containing autoload definition and including some dev requirements to drupal/emr and other components like drupal/entity_meta_audio ...
When requiring drupal/emr what you get in lock is metapackage which depends on drupal/entity_meta_relation
So could be that fixing the dependency from drupal/emr into drupal/entity_meta_relation avoid having that issue?
Hi,
When requiring openeuropa/oe_list_pages which requires drupal/emr we are facing an issue which is a wrong entry in composer autoload_psr4 which is pointing to root src/ directory instead of the relative path to the contrib module.
'Drupal\\emr\\' => array($baseDir . '/src'),
And this is impacting in case of having custom classes for the project under root src/ directory.
When individually requiring drupal/entity_meta_relation 1.2.0 what you get in lock file is not containing autoload definition and including some dev requirements to drupal/emr and other components like drupal/entity_meta_audio ...
When requiring drupal/emr what you get in lock is metapackage which depends on drupal/entity_meta_relation
So could be that fixing the dependency from drupal/emr into drupal/entity_meta_relation avoid having that issue?
Issue related open into Drupal.org Entity Meta Relation contrib module: https://www.drupal.org/project/entity_meta_relation/issues/3253273
The text was updated successfully, but these errors were encountered: