Update redux-form to version 6.7.0 🚀#136
Open
greenkeeperio-bot wants to merge 1 commit intomasterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
redux-form just published its new version 6.7.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of redux-form.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
Bug Fixes
meta.touchedprop fromFieldArray#2836 #2830deleteInWithCleanUpbug #2876 #2875UNREGISTER#2889 #2884Features
initializedprop lets your form component know if it has been initialized yet. #2904 #2901getFormMetaselector to read field metadata such astouchedandvisited. #2859 #2585meta.initialprop toFieldcomponents to know what the initial value was. #2858fieldInputPropTypes,fieldMetaPropTypes,fieldPropTypesforFieldcomponents.defaultShouldValidateanddefaultShouldAsyncValidate#2891 #2890INITIALIZEaction meta data #2835 #2832Maintenance
The new version differs by 933 commits .
f958733v6.7.037ab5aeRemoved trailing commas with prettier496b21dFormatted with better prettier settingsdc80420Added prettier-eslint-cli1c161acadding missing fieldPropTypes exportba30cafFormatted all code with Prettier (#2905)b67edf1Added initialized prop (#2904)99b802eUpdate HandleVsOn.md (#2903)7c6af82passing the last initialValues into initialize action if it is reinitializing the form (#2835)7bd780dExports defaultShouldValidate and defaultShouldAsyncValidate (#2891)2dbd841Add PropTypes for the Field components (#2862)8722fd6Remove references to react-router from doc page. (#2898)e93708bFix deep equal on maps with different structures (#2892)ff213e8Allow direct imports to reduce bundle size. (#2893)cda2572Fancy new npm5 lock file!There are 250 commits in total. See the full diff.