Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Formvalues sectionprefix update #3210

Merged
merged 4 commits into from Jul 19, 2017
Merged

Formvalues sectionprefix update #3210

merged 4 commits into from Jul 19, 2017

Conversation

SBRK
Copy link
Contributor

@SBRK SBRK commented Jul 19, 2017

Since the sectionPrefix is in the context, the connected Component would not update the values of the selector.
Passing the sectionPrefix to the props then adding props to the arguments of the selector fixes that.

@SBRK
Copy link
Contributor Author

SBRK commented Jul 19, 2017

Closes #3202 for good, hopefuly !

@codecov-io
Copy link

codecov-io commented Jul 19, 2017

Codecov Report

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

Impacted file tree graph

@@          Coverage Diff           @@
##           master   #3210   +/-   ##
======================================
  Coverage     100%    100%           
======================================
  Files          68      68           
  Lines        1507    1508    +1     
======================================
+ Hits         1507    1508    +1
Impacted Files Coverage Δ
src/createFormValues.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 cc16406...17d71a5. Read the comment docs.

@erikras erikras merged commit 4cbe5a2 into redux-form:master Jul 19, 2017
@SBRK SBRK deleted the formvalues-sectionprefix-update branch July 19, 2017 14:40
@erikras
Copy link
Member

erikras commented Jul 24, 2017

Published in v7.0.2.

@lock
Copy link

lock bot commented Jun 1, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants