We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
in the current codebase we are using the channel binding object. but we do not have channel bindings. https://github.com/asyncapi/bindings/tree/next-major-spec/http
officially we only have operations and messages biddings and glee should parse them from the operation not channel.
The text was updated successfully, but these errors were encountered:
/progress 10
started working on the issue.
Sorry, something went wrong.
/progress 60 opened a draft PR #579. Will resolve this issue after refactoring the HTTP Adapters.
/progress 90 PR is ready for review.
🎉 This issue has been resolved in version 0.31.1 🎉
The release is available on:
Your semantic-release bot 📦🚀
KhudaDad414
Successfully merging a pull request may close this issue.
Describe the bug
in the current codebase we are using the channel binding object. but we do not have channel bindings. https://github.com/asyncapi/bindings/tree/next-major-spec/http
officially we only have operations and messages biddings and glee should parse them from the operation not channel.
The text was updated successfully, but these errors were encountered: