-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Use PSR-4 in components? #11189
Comments
👍 |
I suggest we benchmark the impact of switching to PSR-4 beforehand. |
@nicolas-grekas the PSR-4 rules are applied before the PSR-0 ones in the composer autoloader, so this should even improve things a bit. |
👍 |
3 similar comments
👍 |
👍 |
👍 |
Working on it |
This was referenced Jun 20, 2014
Closed
3 merges are missing to be complete for symfony |
Tobion
added a commit
that referenced
this issue
Apr 11, 2015
This PR was merged into the 2.7 branch. Discussion ---------- Use PSR-4 everywhere instead of PSR-0 | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #11189 | License | MIT Rebased and updated #12466 Commits ------- 8072213 adjust phpdoc for class not found handler e2bbf07 add phpunit bridge to psr4 60d4994 Tweak classmap paths cc17234 Add two more components to psr-4 17f61af Add psr-4 support to the ClassNotFoundFatalErrorHandler 4e85901 Use PSR-4 everywhere instead of PSR-0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
composer.json
target-dir
is deprecated. Can we switch to PSR-4 in components?The text was updated successfully, but these errors were encountered: