-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
ensure we return null rather than void in SyliusPluginTrait::getContainerExtension #8979
Conversation
Ok .. it seems like the issue is a bit deeper. I run the following:
I assume this is because if the cache is filled (though I don't think my test app actually has the cache enabled .. so wtf?) then it doesn't end up calling the |
@makasim ok its getting stranger .. with the following change the issue with Payum goes way:
|
an alternative fix is
|
3b32eed
to
ebcbbec
Compare
@makasim it looks to me like the |
@lsmith77 Yeah, obviously. I might have a similar case in enqueue. I'll try to debug it there. Hope it is the same issue. |
finally had some more time to look into this .. the issue is that the Again however, the change in this PR should still be applied to Sylius. |
@@ -68,6 +68,8 @@ public function getContainerExtension(): ?ExtensionInterface | |||
if ($this->containerExtension) { |
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.
Maybe just return $this->containerExtension ?: null;
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.
yeah .. I guess that makes things a bit more compact and readable
ebcbbec
to
5d62895
Compare
the errors seem unrelated to the change ... |
…pplication\SyliusPluginTrait::getContainerExtension
5d62895
to
ed6f759
Compare
rebased .. and green |
Thanks Lukas! |
I am not entirely sure what is going on here.
It seems for one that when I implemented a proper Di extension in FOSSyliusImportExportPlugin I suddenly ended up with
Which in turn seems to be caused by suddenly
\Payum\Bundle\PayumBundle\PayumBundle::build
being called twice.Messing around I eventually ended up at:
Which led me to this PR and which magically fixed all the issues I had once I removed all my debug code.