[FIX] settings.range.min and settings.range.max do not inherit manually set date.min and date.max

[uvarov-frontend]

Closes #289

[ghiscoding]

@uvarov-frontend if I look at your PR, it looks like you partially rolled back my previous PR #254 since you removed Date | number input types. However you didn't rolled back the parseDates() changes that I've made in the other PR, so the min/max input might still work with a Date or number? I really wish to keep this, but I haven't tried your new version and it might still work (except for the types that you removed). If you really did remove this functionality, then it should probably added to your new 3.0 roadmap

[uvarov-frontend]

@uvarov-frontend if I look at your PR, it looks like you partially rolled back my previous PR #254 since you removed Date | number input types. However you didn't rolled back the parseDates() changes that I've made in the other PR, so the min/max input might still work with a Date or number? I really wish to keep this, but I haven't tried your new version and it might still work (except for the types that you removed). If you really did remove this functionality, then it should probably added to your new 3.0 roadmap

It didn’t work for date.min/max and range.min/max, so I deleted the types. It doesn’t use ‘parseDates’.

[ghiscoding]

ah ok I'll have to take a look then, I still want to provide these types of input to the min/max settings. Thanks