Skip to content

fix: make Enums usable inside CollectionColumnType #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

RafaelKr
Copy link
Contributor

closes #203

@Kreyu
Copy link
Owner

Kreyu commented Apr 2, 2025

Hey @RafaelKr, thanks for the report and for the pull request. However, I would say CollectionColumnType should not strictly check for enums. I've been checking different scenarios and it looks like the issue occurs for non-scalar values - enums, date time, objects, and much more.

I tried multiple solutions and found a (it seems like) universal one - if there's no property_path or getter in entry_options, I'm defaulting to a getter that simply returns the value, and it works fine. I fixed that in 0.29.2.

Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: Enum inside CollectionColumnType leads to Can't get a way to read the property "0" in class App\MyEnum
2 participants