Doğan Uçar

🚀 #Symfony 7.3 is out - and it is paked with a lot of improvements. The new version remains fully backward-compatible, as promised. But beyond that, #Symfony73 introduces exciting new features across the board: 1/x

* Security upgrades including email #encryption, #OAuth2 introspection * New components: JsonPath, JsonStreamer, ObjectMapper * Massive DX improvements and fine-tuned developer tooling 3/x

🚀 #Symfony 7.3 is out - and it is paked with a lot of improvements. The new version remains fully backward-compatible, as promised. But beyond that, #Symfony73 introduces exciting new features across the board: 1/x

Can #AI find the solution for this issue? I spent way too much time today trying to figure out why defining a constraint on the field "email" kept throwing "This value should be of type string." The configuration looked fine. I just wanted to define a query param like ?email=user@example.com 1/x

PHP attributes don’t allow object instantiations like Type::string() at all. Of course. So, the "solution"? I had to create a custom StringType class that extends Type, just to instantiate it in the attribute. A bit of a hack, but it works. 4/x

Can #AI find the solution for this issue? I spent way too much time today trying to figure out why defining a constraint on the field "email" kept throwing "This value should be of type string." The configuration looked fine. I just wanted to define a query param like ?email=user@example.com 1/x

and make sure it was not blank (NotBlank) and the string in the expected email format (Email) using the known API Platform tools to define a GET route. But no matter what I did, it was not valid. Typed everything again. Cleared cache. Even doubted myself for a second 😄 2/x