-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Documentation wrong? #7427
Comments
@flaushi yes, that's something that was fixed in If you want to help with the docs, send a patch to remove that paragraph :-) |
stollr
added a commit
to stollr/doctrine-orm
that referenced
this issue
Oct 18, 2018
In doctrine#7427 @flaushi mentioned the outdated paragraph. This commit removes this one.
I have created a PR to remove that paragraph ;-) |
Thanks! I wanted to do the same but could not find the paragraph anymore. I tought it had beed deleted already... anyway thanks! |
#7434 merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I randomly found this remark in the FAQs:
https://www.doctrine-project.org/projects/doctrine-orm/en/2.6/reference/faq.html#i-access-a-variable-and-its-null-what-is-wrong
Is this true? All my entities have public fields, and no getters or setters, but doctrine does work fine. Also it is the first time I read that having private/protected fields with getter and setter is a must. Up to now I thought it is more or less a coding standard (and waste of space ;-))
The text was updated successfully, but these errors were encountered: