Closed a-gierczak closed 2 years ago
Hey there, thanks for your PR. We are still analyzing the best way to opt-out from the current behavior of Field. Our internal codebase makes very heavy usage of the current behavior of Field only listening to changes related to its watched field
@fakenickels can we close this PR since that passed 2 years form the last changes?
better close it for now and rediscuss if necessary
This should fix #155. This doesn't extend Field functionality but gives user an option to provide memoized render (e.g. via useCallback) if theirs use case requires it. Also we get rid of annoying bug where Field would render with stale renderProp by default.