-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
A few minor improvements #7113
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
A few minor improvements #7113
Conversation
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.
👍
@@ -365,7 +365,7 @@ Of course, if you know up front that you'll need to access both objects, you | |||
can avoid the second query by issuing a join in the original query. Add the | |||
following method to the ``ProductRepository`` class:: | |||
|
|||
// src/AppBundle/Entity/ProductRepository.php | |||
// src/AppBundle/Repository/ProductRepository.php |
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.
In other chapters (doctrine/repository.rst
, security/entity_provider.rst
, testing/doctrine.rst
), we have the repository classes in the Entity
subnamespace. We should either update them as well or keep this example as is.
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.
best_practices/configuration.rst
on other hand also uses the Repository
namespace.
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.
I think to keep entities and repositories separately is a better option. Let's use the Repository
namespace like in best practices. I'll push more changes
👍 |
1 similar comment
👍 |
Thanks a lot for fixing this inconsistency in the docs, Victor! It's now merged in. |
No description provided.