-
-
Notifications
You must be signed in to change notification settings - Fork 36
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: making it compatible to newer version of @asyncapi/react-component #239
fix: making it compatible to newer version of @asyncapi/react-component #239
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.
@ivangsa |
…capi-preview into upgrade-the-version-of-react-component-and-make-it-compatible
Quality Gate passedIssues Measures |
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.
LGTM! Thanks a lot for this @catosaurusrex2003
I have updated the title of the PR so this is deployed as a patch version
/rtm |
🎉 This PR is included in version 0.6.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Should be merged only after asyncapi/asyncapi-react#1078 is merged.
@asyncapi/react-component
Creating an immature PR for tracking purposes
Related issue(s)
asyncapi/asyncapi-react#1078
#200