Skip to content

fix: fix JMS bindings implementation#5147

Merged
glowcloud merged 4 commits intomainfrom
fix/oss-614-fix-jms-bindings
Mar 30, 2026
Merged

fix: fix JMS bindings implementation#5147
glowcloud merged 4 commits intomainfrom
fix/oss-614-fix-jms-bindings

Conversation

@glowcloud
Copy link
Copy Markdown
Contributor

This PR fixes issues with JMS bindings, which had invalid and missing fields. The fields are now handled in AsyncAPI 2 and 3 namespaces, and in Language Service.

Note: for Server Binding properties field, the type [object] was used as the type provided by the specification does not exist. How the actual object is defined can be seen here.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@glowcloud glowcloud self-assigned this Mar 24, 2026
@glowcloud glowcloud added bug Something isn't working AsyncAPI 2.x AsyncAPI 3.x labels Mar 24, 2026
@glowcloud glowcloud marked this pull request as ready for review March 25, 2026 08:16
@glowcloud glowcloud merged commit d30461e into main Mar 30, 2026
9 checks passed
@glowcloud glowcloud deleted the fix/oss-614-fix-jms-bindings branch March 30, 2026 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AsyncAPI 2.x AsyncAPI 3.x bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants