Me: Why is Doctrine (a PHP ORM) not hydrating my embedded class property? It's marked as embeddable and there are no nullable properties (something which does cause hydration to silently fail apparently). WHY CAN'T I GET THIS TO WORK?!
[a few hours later]
Me: Actually, I can take a different approach and avoid Doctrine embeddables entirely. \o/
Here is a new video of me with an in-depth-tutorial on how #PHP 8.4s new lazy proxies work with a step-by-step example of how I integrated it into the upcoming #DoctrineORM 3.4.
Continuing my first baby steps with video content 🙈 Both kind and brutal feedback welcome in the comments 🤣
Follow-up post on how to use #doctrineorm for Json in #postgresql :
https://www.liip.ch/en/blog/doctrine-orm-support-for-json
Working on the #doctrineorm v1 codebase and its test suite, make you realise how much work has been done on #phpunit, and it simply works! Thank you @sebastian!
At the same time the legacy Doctrine v1 still manages OK-ish in the era of #php8 ! Still with no class namespaces and by implementing its own autoloading system! Is it probably from #php4 times? 🤔
Kudos to the original authors!
(Are they around here BTW?)
Trying to prepare a PR for #doctrineorm and got a weird message from #git
Thank you @greg0ire for starting a first "help-session", but we're still puzzled.
Anybody can reproduce it? Maybe a GIT guru is required 😅
for references: https://github.com/doctrine/orm/issues/11173
Clear, expressive, and type-safe way to represent entity identities by #DDD is to use strongly-typed ID's.
Example in #PHP using #doctrineORM when ID's are generated on client side.
