-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upstream: Extension System, Part IV: Properly register all installed extensions/namespaces in container #61
Comments
Does this sound like the same issue?
And then with ZERO changes to anything, I've run it again;
We see this same issue in lots of places unfortunately. It's only ever on the very first try though, so it affects our CI more than locally. To reproduce you need to;
...and then run the check again. |
🤔 Kind of. But this issue is more to track / try to improve Drupal core's autoloading system which makes this extension easier to maintain |
Hmmmmm is it worth my opening a new issue, or just track/ assist with the core issue? We found that although the patch seemed to address the issue ... it completely broke Drush (with an autoload error). |
Add a test flow for specific contrib
Closing this issue. It's just tracking the Drupal core issue. |
https://www.drupal.org/project/drupal/issues/2941757
The text was updated successfully, but these errors were encountered: