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
The supported mapping types aren't consistent in the extension mapping drivers, sluggable being the worst of it as the attribute driver supports a lot more field types than the XML or YAML drivers, which leads into...
The supported mapping types are generally duplicated for each mapping driver, except for the soft-deleteable extension which has a static helper used by all mappings (and it uses a public static array to check against, meaning downstream users could technically make this whatever they want!)
It'd be good to get the supported field mapping types for each extension consolidated and consistent unless there is a valid reason why datetime_immutable is only supported for attribute mapping when using the sluggable extension 😅
The text was updated successfully, but these errors were encountered:
Two things I'm noticing:
The supported mapping types aren't consistent in the extension mapping drivers, sluggable being the worst of it as the attribute driver supports a lot more field types than the XML or YAML drivers, which leads into...
The supported mapping types are generally duplicated for each mapping driver, except for the soft-deleteable extension which has a static helper used by all mappings (and it uses a public static array to check against, meaning downstream users could technically make this whatever they want!)
It'd be good to get the supported field mapping types for each extension consolidated and consistent unless there is a valid reason why
datetime_immutable
is only supported for attribute mapping when using the sluggable extension 😅The text was updated successfully, but these errors were encountered: