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
Fix generate command when both usePods option and --pod argument is used #7164
Conversation
I agree that this is confusing, but the intent here was that --pod flag negates the value of usePods. So if you had usePods as true you would use --pod to get non-pods. |
Hmm, so what does |
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.
@rwjblue I tend to agree with this patch. Having --pod
disable pod style when --classic
also exists seems very unintuitive.
@Turbo87 - This patch has nothing to do with using both |
I think the point is that the existence of |
I totally agree with you there, but this change would be a breaking change for anyone leveraging the existing behavior. I'd be totally fine with adding a deprecation / warning for anyone that has both |
@emrekutlu can you prepare a PR that prints a warning to the console when |
@emrekutlu - Ping? |
@rwjblue sorry for the wait, I am going to update the pull request this week hopefully. Thanks for pinging. |
…nd --pod flag together
@rwjblue I updated the pull request. |
Thank you! |
Resolves #7163