Add immutableProps option to Field component

[itsuryev]

Fixes #3810

[codecov-io]

Codecov Report

Merging #3849 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #3849   +/-   ##
======================================
  Coverage     100%    100%           
======================================
  Files          70      70           
  Lines        1627    1629    +2     
======================================
+ Hits         1627    1629    +2

Impacted Files	Coverage Δ
src/createField.js	100% <ø> (ø)	⬆️
src/ConnectedField.js	100% <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 b302e6f...2252bc4. Read the comment docs.

[erikras]

Can you add a test to get code coverage back up to 100%?

[itsuryev]

Updated the code, now test coverage is back to 100%.

I might be missing something but I believe that drop in coverage was in error - any assignments in shouldComponentUpdate marked onChange for ReactNative in handleChange as uncovered.

So following decreases coverage:

shouldComponentUpdate(nextProps: Props) {
  const nextPropsKeys = Object.keys(nextProps)
  const thisPropsKeys = Object.keys(this.props)
  const {immutableProps = []} = nextProps

  // or even
  const hello = "world"

And inlining immutableProps usage works fine:

if (~(nextProps.immutableProps || []).indexOf(prop)) {

[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.

[erikras]

Released in v7.4.0.