Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[ProxyManager] isProxyCandidate() does not take into account interfaces#31551
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
nicolas-grekas approved these changesMay 20, 2019
Member
nicolas-grekas left a comment
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.
(but for 3.4 as 2.8 is EOLed)
stof approved these changesMay 20, 2019
…nterfacesWhen using factories it's common best practice to use interface as class name, especially in caseswhere you know impl can differ. Before this fix ProxyManager did not allow these to be lazy.In our case this has lead several to hard to debug issues on classes we need to mark as lazyiand often a need to add lazy on decorators if there are any or other workarounds.As we have had this issue, and still have on both 2.8 and 3.4 this is opened against 2.8.
Member
nicolas-grekas commentedMay 20, 2019
Thank you@andrerom. |
nicolas-grekas added a commit that referenced this pull requestMay 20, 2019
…nt interfaces (andrerom)This PR was merged into the 3.4 branch.Discussion----------[ProxyManager] isProxyCandidate() does not take into account interfaces| Q | A| ------------- | ---| Branch? | 2.8| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets || License | MIT| Doc PR | N/AWhen using factories it's common best practice to use interface as class name, especially in caseswhere you know implementation can differ. Before this fix ProxyManager did not allow these to be lazy.As we have have this issue on 2.8 and 3.4. it's very hard to debug, and goes against best practice for factories to not fix it, this is suggested for 2.8.Commits-------e3739b1 [Bridge\ProxyManager] isProxyCandidate() does not take into account interfaces
This was referencedMay 22, 2019
Merged
Merged
Merged
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using factories it's common best practice to use interface as class name, especially in cases
where you know implementation can differ. Before this fix ProxyManager did not allow these to be lazy.
As we have have this issue on 2.8 and 3.4. it's very hard to debug, and goes against best practice for factories to not fix it, this is suggested for 2.8.