Make strict coercion rule configurable

[fredwu]

After upgrading to Virtus 1.0 which depends on Coercible 0.2.0, we noticed that a bunch of our attributes are now failing due to the stricter coercion rule. For example, a Date field can no longer accept "" (an empty string) because it cannot be coerced. This is especially troublesome in a rails project where attributes can be optional (so they get submitted as empty strings).

Could we make raising UnsupportedCoercion configurable?

For now I have to monkey patch raise_unsupported_coercion to return value directly to get back 0.1.0's behaviour.

Thanks!

[solnic]

Yes this feature is planned for virtus/coercible 1.0.0

[fredwu]

Awesome! 👍

[shepmaster]

👍 This would indeed be useful for the reasons stated by @fredwu.