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

Fix for #188, widget field errors not displaying #193

Merged
merged 1 commit into from
Sep 16, 2015

Conversation

quicksnap
Copy link
Collaborator

While I like the idea of catch, this fixes the problem. It makes sense if the actions are FSAs, since error better not be present if there's no error. Thoughts?

ref: #188

While I like the idea of `catch`, this fixes the problem. It makes sense if the actions are FSAs, since error better not be present if there's no error. Thoughts?

ref: erikras#188
@quicksnap
Copy link
Collaborator Author

As a newcomer, it was an exercise figuring out the pipes in this.. not that it wasn't fun =) However, it may make sense to have form-submission-specific middleware, so that it may simply return a rejected promise, instead of having to code that logic into the component?

@quicksnap
Copy link
Collaborator Author

Or maybe simply a helper for the handleSubmit function argument that checks for x.error and creates a rejection.

erikras added a commit that referenced this pull request Sep 16, 2015
Fix for #188, widget field errors not displaying
@erikras erikras merged commit 35dda22 into erikras:master Sep 16, 2015
@erikras
Copy link
Owner

erikras commented Sep 16, 2015

I like it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants