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

Comparison operators with incompatible types should return undefined instead of raising an exception #96

Open
josephbirkner opened this issue Oct 21, 2024 · 0 comments
Labels
enhancement 🌟 New feature or request

Comments

@josephbirkner
Copy link
Member

Currently, using comparison operators with unsupported pairs of types raises an exception. E.g. 50 > "a" raises a simfil InvalidOperandsException. It would be more practical, if this operation would simply assume the value undefined. This way, a structure like {a: {x: 50}, x: "a"} (containing ambiguous value types for the same field name) could more easily be matched with a query like **.x > 0.

@josephbirkner josephbirkner added the enhancement 🌟 New feature or request label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 🌟 New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant