Operators.In and Operators.NotIn with not working properly when trying to match the rule setting the condition value as null

[isabelneto]

Description

The problem with the IN and NOT IN operators when trying to match the rule by setting the condition value to null had as its root cause the fact that the default values defined for the array types were an empty array and should be its elementary types.

Fixed defaults for array types to the elementary types (int, decimal, bool and string).

Closes #130

Change checklist

• Code follows the code rules guidelines of this project
• Commit messages follow the commit rules of this project
• I have self-reviewed my changes before submitting this pull request
• I have covered new/changed code with new tests and/or adjusted existent ones
• I have made changes necessary to update the documentation accordingly

Please also check the I want to contribute guidelines and make sure you have done accordingly.

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

[luispfgarces]

Seems to be OK by me (I tested it locally to understand your resolution). It seems to me then that we don't really need to differentiate DataTypes from String and ArrayString (and the other ones). But we can look into that another time, this definitely solves the problem and I think nothing else is required 👌