-
Notifications
You must be signed in to change notification settings - Fork 83
Symfony 4 compatibility #420
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
Conversation
f7741b1
to
3cf40ff
Compare
2bfb179
to
5ff8d54
Compare
14b6751
to
3dfbad1
Compare
the remaining test failures are all about
|
…nfiguration with new symfony versions
86fc261
to
04e1069
Compare
04e1069
to
00af897
Compare
|
||
<service id="fos_http_cache.command.refresh_path" class="FOS\HttpCacheBundle\Command\RefreshPathCommand"> | ||
<argument type="service" id="fos_http_cache.cache_manager" /> | ||
<tag name="console.command"/> |
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.
this is missing the "command" attribute compared to the other command. but since you set the static property now, you don't need to specify the command name in the services anymore
|
||
/** | ||
* If no cache manager is specified explicitly, fos_http_cache.cache_manager | ||
* is automatically loaded. | ||
* | ||
* @param CacheManager|null $cacheManager The cache manager to talk to | ||
* @param string $commandName Name of this command, in case you want to reuse it | ||
* @param string $commandName Deprecated: Do not set this parameter. | ||
*/ | ||
public function __construct(CacheManager $cacheManager = null, $commandName = 'fos:httpcache:invalidate:path') |
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.
a better deprecation would be to remove the argument and use func_get_arg logic as fallback and triggering a deprecation when it was passed
@dbu Any clue when |
@XWB i am trying to wrap up some other things like #430 but hope that after that i can release. one big issue is symfony/symfony#25736 (comment) - if you have time to look into this and maybe come up with a solution, that would be great. |
@dbu Yes we suffered the same issue after upgrading to Symfony 3.4, but we hacked around it in the Varnish config. If
Later on, we switch back to private:
Perhaps @nicolas-grekas has a better solution. Until then, the hack works just fine. |
FTR: Symfony 4.1 introduced a special header to tell the session listener to not overwrite visibility in symfony/symfony#26681 we use that since #439 |
Symfony 4 compatibility based on this article.
ServiceTest::testCanBeLoaded
=> guess we should use the container builder instead of the compiled container in that test. most of those services need not be public probably.