[HttpKernel] Deprecate the Kernel name #28809
Conversation
fabpot
commented
Oct 10, 2018
| Q | A |
|---|---|
| Branch? | master |
| Bug fix? | no |
| New feature? | yes |
| BC breaks? | no |
| Deprecations? | yes |
| Tests pass? | yes |
| Fixed tickets | #26904 |
| License | MIT |
| Doc PR | n/a |
| @@ -421,7 +428,7 @@ protected function build(ContainerBuilder $container) | |||
| */ | |||
| protected function getContainerClass() | |||
| { | |||
| return $this->name.ucfirst($this->environment).($this->debug ? 'Debug' : '').'ProjectContainer'; | |||
| return 'app'.ucfirst($this->environment).($this->debug ? 'Debug' : '').'ProjectContainer'; | |||
There was a problem hiding this comment.
shouldn't we keep using it for now, for BC ? Otherwise, it would be a BC break for people using multiple kernels (with different names) and expecting to have the container classes not clashing together.
There was a problem hiding this comment.
You mean when a multi-kernel app share the same cache?
There was a problem hiding this comment.
I don't think this is worth it. As of Symfony 4.x, we are only supporting Flex (so, doing it in 3.4 was not possible, but I think this is totally legitimate now).
ce81b5b to
59048e2
Compare
| @@ -421,7 +428,7 @@ protected function build(ContainerBuilder $container) | |||
| */ | |||
| protected function getContainerClass() | |||
| { | |||
| return $this->name.ucfirst($this->environment).($this->debug ? 'Debug' : '').'ProjectContainer'; | |||
| return 'app'.md5(get_class($this)).ucfirst($this->environment).($this->debug ? 'Debug' : '').'ProjectContainer'; | |||
There was a problem hiding this comment.
Could this potentially break existing applications with multiple kernels?
There was a problem hiding this comment.
How? Each Kernel class must have a different FQCN anyway, so it's still unique.
There was a problem hiding this comment.
Having additional arguments in the application kernel class that are different for each instance does work too, doesn't it?
There was a problem hiding this comment.
It can work, but this won't break with my change as in this case, the cache cannot be shared between apps (today already).
There was a problem hiding this comment.
This will break apps rely on the kernel name to create "virtual" kernels. For example, I've some projects based on this idea https://github.com/yceruto/symfony-skeleton-vkernel.
I don't know whether this practice is right or not, but it simplify our projects sharing vendors, config and src. It work well thank to the kernel name and just one Kernel class.
There was a problem hiding this comment.
Then, you need to override the getContainerClass().
|
tests are failing |
|
Tests fixed |
This PR was merged into the 4.2-dev branch. Discussion ---------- [HttpKernel] Deprecate the Kernel name | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? | yes <!-- don't forget to update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | #26904 | License | MIT | Doc PR | n/a <!-- Write a short README entry for your feature/bugfix here (replace this comment block.) This will help people understand your PR and can be used as a start of the Doc PR. Additionally: - Bug fixes must be submitted against the lowest branch where they apply (lowest branches are regularly merged to upper ones so they get the fixes too). - Features and deprecations must be submitted against the master branch. --> Commits ------- 98ff750 [HttpKernel] deprecated the Kernel name
| @@ -421,7 +428,7 @@ protected function build(ContainerBuilder $container) | |||
| */ | |||
| protected function getContainerClass() | |||
| { | |||
| return $this->name.ucfirst($this->environment).($this->debug ? 'Debug' : '').'ProjectContainer'; | |||
| return str_replace('\\', '_', \get_class($this)).ucfirst($this->environment).($this->debug ? 'Debug' : '').'Container'; | |||
There was a problem hiding this comment.
This change breaks BC by removing the "name" (the basename of the project_dir really) from the dimensions that compose separate namespaces.
This is why the CI is red (and was also caught before merging ;) )
Side note: the container class is also a legacy concept; its real name is random (it's the hash of its contents actually.)
The only real remaining use case of the container class is for generating the name of the file that serves as entry point for loading the container.
This PR was merged into the 4.2-dev branch. Discussion ---------- [HttpKernel] fix kernel.name deprecation | Q | A | ------------- | --- | Branch? | 4.2 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | - | License | MIT | Doc PR | - Finishes #28809 and makes tests green again. Commits ------- 4964ffc [HttpKernel] fix kernel.name deprecation
This PR was squashed before being merged into the 4.2-dev branch (closes #28939). Discussion ---------- [WebProfilerBundle] Remove application name | Q | A | ------------- | --- | Branch? | master | Bug fix? | yes | New feature? | yes | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? | yes | Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | #... <!-- #-prefixed issue number(s), if any --> | License | MIT | Doc PR | symfony/symfony-docs#... <!-- required for new features --> This fixes a regression in master, i think after #28809 (or something related) There's still a "application name" concept out there today, and it's `ConfigDataCollector::getApplicationName()` 🤔 In my case the service resolved to ```php $e = new \Symfony\Component\HttpKernel\DataCollector\ConfigDataCollector(\basename('/app')); ``` Causing the app name to be, well, `app` (again :P). It was really confusing. Before:  (the "a" is from "app" here) After:  or  I think we need to deprecate the argument for real? cc @fabpot Commits ------- f5c355e [WebProfilerBundle] Remove application name
