-
-
Notifications
You must be signed in to change notification settings - Fork 16
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: remove obsolete try...catch
#176
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
40d8e2e
to
a2ac491
Compare
a2ac491
to
ce84ad6
Compare
I do not normally do Either that use case has already been taken care of, or I will see the same edge case and process it in another way. @Souvikns, this PR looks good to me, but can you please do this simple review only so I'm not reviewing my own code? |
/rtm |
🎉 This PR is included in version 0.5.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Issue asyncapi/cli#1475 gives an example where an invalid external reference is ignored, and all other documents are skipped. Instead of silently failing, this PR proposes to let the error propagate.
Related issue(s)
Fixes asyncapi/cli#1475