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

topdown/type: Fix inconsistent is_<type> return values. #5064

Conversation

philipaconrad
Copy link
Contributor

This PR adjusts the implementation of all of the is_<type> builtins to consistently return only true/false values. This change is identical to the *.is_valid behavior changes that landed back in #4844.

The affected builtins are:

Fixes: #4943

Fixes open-policy-agent#4943

Signed-off-by: Philip Conrad <philipaconrad@gmail.com>
@philipaconrad philipaconrad force-pushed the issue-4943-fix-is-valid-functions branch from f0ee933 to 370c1a8 Compare August 29, 2022 22:01
@philipaconrad
Copy link
Contributor Author

@ashutosh-narkar I forgot to fix the WASM side for these builtins. Fix coming shortly...

Signed-off-by: Philip Conrad <philipaconrad@gmail.com>
@srenatus srenatus merged commit a8de6a2 into open-policy-agent:main Aug 30, 2022
@philipaconrad philipaconrad deleted the issue-4943-fix-is-valid-functions branch September 14, 2022 20:26
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.

is_number does not correctly return false (also the other is_ type checking builtins)
3 participants