Fix async/submit errors getter for nested fields

[xcrzx]

asyncErrors & submitErrors are flat key-value objects: { 'field.a.b.c': 'error' }, so we should escape field name in order to get data from it.

[codecov-io]

Codecov Report

Merging #3755 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #3755   +/-   ##
======================================
  Coverage     100%    100%           
======================================
  Files          70      70           
  Lines        1578    1578           
======================================
  Hits         1578    1578

Impacted Files	Coverage Δ
src/ConnectedField.js	100% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 90fdd65...d16f1e2. Read the comment docs.

[erikras]

Doesn't this work, too, and is better?

asyncError: getIn(formState.asyncErrors, name),

[xcrzx]

Unfortunately not.

const formState = {
    asyncErrors: {
        'a.b.c': 'Error message',
    }
};

const name = 'a.b.c';

getIn(formState, `asyncErrors['${name}']`); // 'Error message'
getIn(formState.asyncErrors, name); // undefined

Following code getIn(formState.asyncErrors, 'a.b.c') is trying to access formState.asyncErrors.a.b.c while actually we need formState.asyncErrors['a.b.c']

[erikras]

Published in v7.2.1.

[sergeyfedotov]

It's a breaking change. Before v7.2.1 only nested error object could be used.

[dagstuan]

This should have been released as 8.0.0 as this is a breaking change.

[erikras]

Apologies for this accidental breaking change... it should be rolled back (unbroken).

[erikras]

Reverted this change in v7.2.2, as it broke several things. Let's discuss how to accomplish what you need to.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.