and not a bit a more readable or at least an UTF-8 encoded name?
\n(as far as I can see the file is new in Symfony 6.1.0).
It's a \"cookie\" class, one with a unique distinct super-short name, internal also, needed for technical reasons (namely minimizing the size of the serialized payload).
\nI made it non-utf8 on purpose, to have a single-char class-name that has low collision chance.
Strange class name in ValueWrapper.php #46477
-
|
Is there a special reason why there is in the file: src/Symfony/Component/Cache/Traits/ValueWrapper.php the ISO-8859-1 encoded line: and not a bit a more readable or at least an UTF-8 encoded name? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
|
It's a "cookie" class, one with a unique distinct super-short name, internal also, needed for technical reasons (namely minimizing the size of the serialized payload). |
Beta Was this translation helpful? Give feedback.
-
|
No I didn't experience any so far, but from a theoretical point of view / Murphy I can imagine that something can go wrong in the future. |
Beta Was this translation helpful? Give feedback.
-
|
As a side note you are now using multiple encodings as in e.g. ./src/Symfony/Component/Validator/Constraints/Isin.php (i.e. it is in a comment though) there is the name Masforné in UTF-8 encoding. |
Beta Was this translation helpful? Give feedback.
-
|
Unearthing this: for some reason, after doing the composer require stuff to get the cache on Windows 11 / NTFS, files get to be using UTF-8 judging from editor, but after the clone, I always get Only solution I found on both project is to trash the The Unicode Note: this was after requiring Just letting this comment in case someone else stumbles on this. |
Beta Was this translation helpful? Give feedback.
-
I've experienced. Also i try to use Buggregator and it's require json encoded report. But it's impossible to json encode ( Seems like this feature makes it impossible to profiling Symfony application when using Symfony cache. 
Could you suggest something, @nicolas-grekas? |
Beta Was this translation helpful? Give feedback.
-
|
That's an issue with both tools, nothing forces using UTF-8 for class names. |
Beta Was this translation helpful? Give feedback.
-
|
its not something to be fixed on the symfony side, but just to give you an idea: the autoloader in the REDAXO project uses a json cache file for the autoloader, which does not work with non-UTF8 stuff. I try to fix it at the REDAXO end though. see german issue: redaxo/redaxo#5780 |
Beta Was this translation helpful? Give feedback.
-
|
By using such a character, you deliberately break PSR-1. https://www.php-fig.org/psr/psr-1/
I don't think it is very unreasonable that other tools expect to see UTF-8 everywhere in 2025. It is one option to state "all those other tools are at fault, they should be generalised enough to support all kinds of charsets." Another option would be to stop using the character and do UTF-8 like everyone else. |
Beta Was this translation helpful? Give feedback.
It's a "cookie" class, one with a unique distinct super-short name, internal also, needed for technical reasons (namely minimizing the size of the serialized payload).
I made it non-utf8 on purpose, to have a single-char class-name that has low collision chance.