Skip to content
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

Docs: clarify consequence of using autoGenerateProxyClasses with %debugMode% #99

Open
dakur opened this issue May 26, 2022 · 2 comments

Comments

@dakur
Copy link

dakur commented May 26, 2022

In docs, there is a statement:

image

But there is no mention about that orm:generate-proxies has to be run on production otherwise the application will fail.

Mine fail when fixtures were applying.

@dakur dakur changed the title autoGenerateProxyClasses config: make a note that this require Clarify consequence of using autoGenerateProxyClasses with %debugMode% May 26, 2022
@dakur dakur changed the title Clarify consequence of using autoGenerateProxyClasses with %debugMode% Docs: clarify consequence of using autoGenerateProxyClasses with %debugMode% May 26, 2022
@f3l1x
Copy link
Member

f3l1x commented Dec 16, 2022

Hi ✋ I think we can reference original doctrine docs, what do you think?

@dakur
Copy link
Author

dakur commented Dec 16, 2022

Yes, as a point of reference yes. But the problem with %debugMode% must be explained in-place. Something like:

Note that in case of autoGenerateProxyClasses is resolved to false (in production mode), proxy entities have to be generated manually with CLI command. Refer to doctrine docs for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants