So I have a User entity in a #Symfony project with an int type $id property. And something deep in the framework is trying to assign a string value to the $id which is throwing critical type errors.
WTH. Am I supposed to make User::$id a string|int type? No thanks. It's in the framework so out of my hands. Some token unserializing step.
@thgs I added a setId() method to the User class that takes an int or string & casts it. Hoping that will get called automatically by whatever caused that error.
@syntaxseed Callstack doesn't help? Xdebug helps me a lot with those. I've been doing mappings like that all day today. I break early and go step by step
@syntaxseed My guess: Your getUserIdentifier() method inside of your User returns the $id. However, the getUserIdentifier method should return something like email or username.
Uncaught PHP Exception TypeError: "Cannot assign string to property App\Entity\User::$id of type ?int" at /vendor/symfony/security-http/Firewall/ContextListener.php line 267
@syntaxseed cant you treat it as a string, and unmarshall yourself?
There are so many reasons I'd want app code to treat a primary key as a string; and only want the nitty gritty of int etc at the outer layer & storage.
Not all strings are ints, but I've never seen a primary key without a string representation available.
I've also never seen anyone represent a uuid, snowflake id, or other primary key as a single int successfully.
Add comment