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

Don't use reject for expected outcomes. #507

Merged
merged 1 commit into from
Jun 7, 2017

Conversation

rstuart85
Copy link
Contributor

Instead, communicate a failure of validation using a param to resolve.

See issue #506

Instead, communicate a falure of validation using a param to resolve.

See issue logaretm#506
@logaretm
Copy link
Owner

I understand the need for not wanting to catch the exceptions, still what about backward compatibility? I prefer if we can provide an option to let it "soft" reject them using your PR, otherwise it would throw so users can choose which behavior seems reasonable to them.

@logaretm logaretm merged commit 58ea1ac into logaretm:master Jun 7, 2017
@kevenjesus
Copy link

I have 2 forms on the same page, so I have 2 different scopes and for that I create 2 keys within the date (), AI at that time that happens the error

https://jsfiddle.net/2sjf0mv7/2/

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.

None yet

3 participants