Data - complex story range filter about grommet HOT 1 CLOSED

There are two problems here related to RangeSelectors in DataFilters.

1. For complex, hierarchical property names that we support in forms like 'economy.GDP', DataForm's transformTouched specially treats RangeSelector values since it's looking for _range in the value object, but how it finds this in touched assumes only 1 level of property name. This is easy to fix.
2. DataFilters decides whether to have a # of filters badge based on how many non-falsey things end up in touched as returned by transformTouched. But any property value in the form set back to it's initial value can be truthy if that initial value is something, especially true for RangeSelectors which will always have a value. Should DataFilters instead determine touched by comparing against initial/default values? Or is that something the badge calculation should do? I'm thinking the badge calc filter should compare against initial/default values for filters instead.

from grommet.