Add form.getTouchedFieldsValue helper

[mgcrea]

Add form.getTouchedFieldsValue helper

[zombieJ]

Hmmm. Not sure if we could provides getFields function out for user to filter themself since there are lots of getXXXFieldsValue if we provide this api.

[mgcrea]

Maybe with a more generic filterFieldsValue that would take a callback?

filterFieldsValue([], meta => meta.touched)

We could also drop the first arg (nameList) and have (name, meta) as the callback signature to let the user eventually filter by name. That would probably be even more elegant:

filterFieldsValue((name, meta) => optionalNameList.includes(name) && meta.touched)

Or another naming you would find more suitable, some ideas:

• getFieldsValueByMeta
• filterFieldsValueByMeta
• filterFieldsValue (cleaner, would be my pick)

If you are good with such changes, I'll happily rework the PR.

[zombieJ]

How about getFieldsValue([nameList?: NamePath[],] filterFunc?: (meta: Meta) => boolean)?

cc @afc163 @yesmeck @chenshuai2144

[mgcrea]

Looks clean with minimal API surface change 👍

[mgcrea]

@zombieJ any update regarding this? Could work on a PR with your latest API.

[zombieJ]

Yes, please.

[mgcrea]

@zombieJ I've updated the PR #44 with the new API, looking forward to hear your feedback.