You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if it is covered by the "Future H)" item of #102 issue but I've noticed that LiveComponent crash when trying to (de)hydrate Uuid.
More precisely, in LiveComponentHydrator#dehydrateObjectValue() method, line 507, (new PropertyInfoExtractor([new ReflectionExtractor()]))->getProperties($classType) returns null which makes the foreach loop crash.
This is quite annoying when using Uuid in a DTO class that mixed entities and simple DTOs. I could use useSerializerForHydration option on LineProp but then I would need to manage serialization in my entity which can be a burden.
I will try to get through this by creating an Hydration Extension for Uuid but I think this would be a nice addition if it could be managed by Live Component natively.
The text was updated successfully, but these errors were encountered:
Well, as it is a dehydration of the Uuid object (from symfony/uid package), I don't think I would change anything. In fact, my UuidHydrationExtension workaround works pretty well :
I am not sure which package should have the responsibility to handle this compatibility problem between symfony/ux-live-component and symfony/uid packages ? Probably symfony/ux-live-component but for some reason it is not obvious to me :/
I'm not sure if it is covered by the "Future H)" item of #102 issue but I've noticed that LiveComponent crash when trying to (de)hydrate Uuid.
More precisely, in LiveComponentHydrator#dehydrateObjectValue() method, line 507,
(new PropertyInfoExtractor([new ReflectionExtractor()]))->getProperties($classType)
returns null which makes the foreach loop crash.This is quite annoying when using Uuid in a DTO class that mixed entities and simple DTOs. I could use
useSerializerForHydration
option on LineProp but then I would need to manage serialization in my entity which can be a burden.I will try to get through this by creating an Hydration Extension for Uuid but I think this would be a nice addition if it could be managed by Live Component natively.
The text was updated successfully, but these errors were encountered: