-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[HttpKernel] Clarify deprecation of non-scalar values in surrogate fragment renderer #19281
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
[HttpKernel] Clarify deprecation of non-scalar values in surrogate fragment renderer #19281
Conversation
chalasr
commented
Jul 4, 2016
Q | A |
---|---|
Branch? | 3.1 |
Bug fix? | no |
New feature? | no |
BC breaks? | no |
Deprecations? | no |
Tests pass? | yes |
Fixed tickets | #19262 |
License | MIT |
Doc PR | ~ |
@@ -65,7 +65,7 @@ public function render($uri, Request $request, array $options = array()) | |||
{ | |||
if (!$this->surrogate || !$this->surrogate->hasSurrogateCapability($request)) { | |||
if ($uri instanceof ControllerReference && $this->containsNonScalars($uri->attributes)) { | |||
@trigger_error('Passing objects as part of URI attributes to the ESI and SSI rendering strategies is deprecated since version 3.1, and will be removed in 4.0. Use a different rendering strategy or pass scalar values.', E_USER_DEPRECATED); | |||
@trigger_error('Passing objects or arrays as part of URI attributes to the ESI and SSI rendering strategies is deprecated since version 3.1, and will be removed in 4.0. Use a different rendering strategy or pass scalar values.', E_USER_DEPRECATED); |
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.
What about "Passing non scalar values [...]" instead?
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.
I hesitated because it is already written "pass scalar values" at the end, but if you think it is clearer, let's use it.
We should update the upgrade files too. |
729701b
to
e8ea461
Compare
I did the change. |
👍 |
@chalasr The |
…nderer Update UPGRADE-3.1 too Use non-scalar values as deperecated type Update UPGRADE-4.0 too
e8ea461
to
b088978
Compare
I missed it, it's ok now @xabbuh. |
👍 |
Thank you @chalasr. |
… surrogate fragment renderer (chalasr) This PR was merged into the 3.1 branch. Discussion ---------- [HttpKernel] Clarify deprecation of non-scalar values in surrogate fragment renderer | Q | A | ------------- | --- | Branch? | 3.1 | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #19262 | License | MIT | Doc PR | ~ Commits ------- b088978 [HttpKernel] Clarify deprecation of non-scalar values in surrogate renderer
…ragment renderer (chalasr) This PR was merged into the 3.1 branch. Discussion ---------- [HttpKernel] Fix assertion of deprecation in surrogate fragment renderer | Q | A | ------------- | --- | Branch? | 3.1 | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | n/a | License | MIT | Doc PR | n/a The message has been changed in #19281 but not the corresponding assertion Commits ------- 4245bac [HttpKernel] Fix assertion of deprecation in fragment renderer