Doğan Uçar
@dogano.bsky.social
Founder | Creator of Keestash | Opinions are my own.
🚀 #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
The new version remains fully backward-compatible, as promised.
But beyond that, #Symfony73 introduces exciting new features across the board:
1/x
June 1, 2025 at 10:40 AM
🚀 #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
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
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
May 21, 2025 at 8:00 PM
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
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