Skip to content
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

Coercion logic does not handle Enum type correctly. #2517

Closed
hatyo opened this issue Feb 16, 2024 · 0 comments · Fixed by #2518
Closed

Coercion logic does not handle Enum type correctly. #2517

hatyo opened this issue Feb 16, 2024 · 0 comments · Fixed by #2518
Assignees
Labels
bug Something isn't working planner Related to the query planner

Comments

@hatyo
Copy link
Contributor

hatyo commented Feb 16, 2024

In Cascades, the logic for handling coercion of Type.Enum is missing, and it should be fixed by adding basic no-op rules that permit the following no-op coercions:
For a given Enum E1:

  • nullable E1 to nullable E1 (enum to itself)
  • not nullable E1 to not nullable E1 (enum to itself)
  • not nullable E1 to nullable E1 (this is fine since the nullable E1's domain can accommodate for all elements in E1.
@hatyo hatyo added bug Something isn't working planner Related to the query planner labels Feb 16, 2024
@hatyo hatyo self-assigned this Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working planner Related to the query planner
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant