-
-
Notifications
You must be signed in to change notification settings - Fork 454
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 a modern directory structure #1767
Conversation
fcfdd77
to
60b516b
Compare
The Psalm failures demonstrate another reason why this is better: the Lines 23 to 33 in 7150c1d
|
yes, this is welcome |
I'm unsure where the 2 svg files should go. Should they go into DoctrineBundle/Resources/views/Collector/db.html.twig Lines 11 to 15 in 7150c1d
|
Keep them in templates. And let's target next minor. |
Will address the conflicts once #1768 is merged and merged up. |
The recommended directory structure is more similar to what we do in non-bundle repositories. Also, this means smaller configuration for tools such as PHPCSStandards, PHPUnit or Psalm.
60b516b
to
a051359
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To support the modern structure, the DoctrineBundle class needs to be updated to override the getPath()
method (or to extend AsbtractBundle which already does the override) as the bundle class is not at the root path of the bundle anymore.
} | ||
}, | ||
"autoload-dev": { | ||
"psr-4": { | ||
"": "Tests/DependencyInjection" | ||
"": "tests/DependencyInjection", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this seems to be about autoloading the Fixtures
namespace, I would suggest using Fixtures\\
as the PSR-4 prefix (and going one level deeper for the path) instead of a fallback for any class.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 will do in a separate PR
@ostrolucky why did you merge? Is that not an issue? |
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
Addressed in #1770 |
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
This is required when the bundle class is not at the root path of the bundle, which is the case since doctrine#1767
The recommended directory structure is more similar to what we do in non-bundle repositories.
Also, this means smaller configuration for tools such as PHPCSStandards, PHPUnit or Psalm.
Although this is no bugfix, I'm targeting 2.11.x so that merging up does not become a nightmare.