Problem/Motivation

Follow up from #3256642: Introduce database driver extensions and autoload database drivers' dependencies.

That issue introduce database driver extensions that can autoload dependencies.

In this issue, add autoload directory for the parent database driver modules in Composer::preAutoloadDump.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3366852

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mondrake created an issue. See original summary.

govind_giri_goswami made their first commit to this issue’s fork.

govind_giri_goswami’s picture

Assigned: Unassigned » govind_giri_goswami
Status: Active » Needs review
govind_giri_goswami’s picture

The modification adds autoload directories for the parent database driver modules (Drupal\mysql and Drupal\pgsql) using the PSR-4 autoload standard. These directories are specified relative to the Drupal core/modules directory. The remaining parts of the method, which handle the addition of classmap entries for other dependencies, remain unchanged

smustgrave’s picture

Status: Needs review » Needs work
Issue tags: +Needs issue summary update

This needs an issue summary update.

Reading the parent issue talks about conditionally adding. The MR seems to load both drivers no matter what. Is that really desired?

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.