Config option for turning off custom scope argument sanitization

[garettarrowood]

There has been a lot of discussion about ways to get around Ransack converting scope values to booleans. Here are just a few places: #509, #593, #580, #566. This PR specifically addresses the tests presented in #575.

An easy solution to this would be to simply stop making these conversions. But then we run the risk of breaking backwards compatibility. So instead of changing them, I've added a config option to turn them off.

It'd be easy to modify this to make the config option more granular. We could set it up for the user to specify what exact truthy/falsey values they would like converted, and use the default settings if this config is NOT specified. For example, instead of:

    # Ransack.configure do |config|
    #   # Accept my custom scope values as what they are.
    #   config.sanitize_custom_scope_booleans = false
    # end

we could do this:

    # Ransack.configure do |config|
    #   # Only convert these values to booleans
    #   config.truthy_values_to_convert_in_custom_scopes = ['TRUE', 'true', '1']
    #   config.falsey_values_to_convert_in_custom_scopes = ['FALSE', 'no way no how']
    # end

But I don't know if that level of detail is needed/desired. If being able to disable boolean conversion is not enough, this could be added later on.

[truonglocbinh93]

@garettarrowood I added your config but error when start server Is there any solution for this problem? Please help me.

[stevebissett]

This was really helpful today. Thank you @garettarrowood 🏆