feat(containers/ComponentForm): Call onChange/onSubmit props#3389
Merged
feat(containers/ComponentForm): Call onChange/onSubmit props#3389
Conversation
3be8396 to
0ccc38b
Compare
Contributor
|
Size Change: +31 B (0%) Total Size: 2.24 MB
ℹ️ View Unchanged
|
Contributor
frassinier
approved these changes
Aug 18, 2021
sgangnant
approved these changes
Aug 18, 2021
Merged
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.
What is the problem this PR is trying to solve?
It's not possible to use onChange/onSubmit props with the containers component, which is needed for some use case where we don't want to rely on sagas
What is the chosen solution to this problem?
add support for props.onSubmit and props.onChange in the container
Please check if the PR fulfills these requirements
[ ] This PR introduces a breaking change