Symfony: Breaking change using array values in cookies since Symfony v3.3
| Q | A
| ---------------- | -----
| Bug report? | yes
| Feature request? | no
| BC Break report? | yes
| RFC? | yes
| Symfony version | 3.3.*
Please see this issue for details and code snippets.
thomxc
😕1
👎1
>All comments
Passing array values as the cookie value was never supported in Symfony. The contract in Symfony 3.2 and older is string only: https://github.com/symfony/symfony/blob/3.2/src/Symfony/Component/HttpFoundation/Cookie.php#L38
For 3.3, we actually changed it to allow string|null.
Btw, I don't see how this could work in 3.2 either. AFAICT, it should also be triggering a Array to string conversion notice, as it also casts the value to string in 3.2
stof
on 1 Jun 2017
👍2
Was this page helpful?
0 / 5 - 0 ratings
Related issues
patrick-mcdougle
路
3Comments
meyerbaptiste
路
3Comments
ryan0x44
路
3Comments
ghost
路
3Comments
FRAGnatt
路
3Comments
Most helpful comment
Passing array values as the cookie value was never supported in Symfony. The contract in Symfony 3.2 and older is
stringonly: https://github.com/symfony/symfony/blob/3.2/src/Symfony/Component/HttpFoundation/Cookie.php#L38For 3.3, we actually changed it to allow
string|null.Btw, I don't see how this could work in 3.2 either. AFAICT, it should also be triggering a
Array to string conversionnotice, as it also casts the value to string in 3.2