Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[FrameworkBundle] HttpCache is not longer abstract#26356
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
stof commentedMar 1, 2018
this was never necessary AFAICT. It looks like a mistake by trying make it parallel to AppKernel extending the Symfony class, while there was actually nothing to implement in AppCache from day one. |
stof commentedMar 1, 2018
However, this class has a typehinting issue in the constructor. It typehints HttpKernelInterface, but the implementation actually expects a KernelInterface (which has much more methods) |
lyrixx commentedMar 1, 2018
So is it a bug fix ? |
nicolas-grekas commentedMar 14, 2018
lets' make it a bug fix and fix the type hint? |
lyrixx commentedMar 14, 2018
OK, I will do that |
lyrixx commentedMar 14, 2018
done |
| /** | ||
| * @paramHttpKernelInterface $kernel AnHttpKernelInterface instance | ||
| * @param string$cacheDir The cache directory (default used if null) | ||
| * @paramKernelInterface $kernel AnKernelInterface instance |
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.
- An KernelInterface instance+ A KernelInterface instance
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.
Fixed
javiereguiluz commentedMar 16, 2018
I'm confused: is this a bug fix or a new feature? The branch is |
lyrixx commentedMar 16, 2018 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@javiereguiluz I updated the PR to be a "bug fix" as requested. Indeed the milestone should be changes. And this change does not require any change in end-users code. |
nicolas-grekas commentedMar 16, 2018
Thank you@lyrixx. |
This PR was merged into the 2.7 branch.Discussion----------[FrameworkBundle] HttpCache is not longer abstract| Q | A| ------------- | ---| Branch? | master| Bug fix? | no| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets || License | MIT| Doc PR |---I don't really know why this class was abstract in the first place.But it's not needed. A fresh symfony 4 application can use this classdirectly without extending it.Commits-------4d075da [FrameworkBundle] HttpCache is not longer abstract
fabpot commentedMar 16, 2018
How is this a bug? This is definitely a "new feature". It does not fix anything. |
lyrixx commentedMar 16, 2018
@fabpot initially the PR targeted master. But Nikos asked me to put it as a bug fix.
WDYT? Should I revert the PR and re-open a new one against master ? |
fabpot commentedMar 21, 2018
"But I thinks it does not harm" is exactly what I don't like. If we start doing that, most PRs do not harm (at least, that's the initial reasoning), but something it does. So, we should follow our policy strictly: only bug fixes on non-master branches. In this case, I would revert the abstract change in all branches but master (you can do that directly in the code without PRs as it would mean 2 extra PRs). |
lyrixx commentedMar 21, 2018 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Ok I got it. Sorry about that. I have added6073066 to the 2.7 branch. I wanted to merge 2.7 in 2.8 but there was conflicts about other changes. I'm not really able to solve theme :/ Thanks |
I don't really know why this class was abstract in the first place.
But it's not needed. A fresh symfony 4 application can use this class
directly without extending it.