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: do not catch error #247

Closed
wants to merge 1 commit into from
Closed

Conversation

fxxjdedd
Copy link
Contributor

Hello @yiminghe ,
The exception is caught here but not thrown. Is there any reason? Or it's a bug?

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Hello @yiminghe ,
The exception is caught here but not thrown. Is there any reason? Or it's a bug?
@fxxjdedd fxxjdedd changed the title fix: dont't catch error fix: do not catch error Jul 22, 2020
@yiminghe
Copy link
Owner

yiminghe commented Aug 5, 2020

Do not want to pollute console or trigger error report. error should be handled by asyn-validator caller

@yiminghe yiminghe closed this Aug 5, 2020
@fxxjdedd
Copy link
Contributor Author

fxxjdedd commented Aug 5, 2020

That's fair. But sometimes, users may make some stupid mistakes, and these mistakes are not thrown out, making it difficult for users to debug errors.

@yiminghe
Copy link
Owner

yiminghe commented Aug 5, 2020

That's fair. But sometimes, users may make some stupid mistakes, and these mistakes are not thrown out, making it difficult for users to debug errors.

by default, errors are warned: Schema.warning

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

2 participants