feat(ls): update Anypoint MQ Bindings#5128
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
| const destinationTypeTypeLint: LinterMeta = { | ||
| code: ApilintCodes.ASYNCAPI2_ANYPOINTMQ_CHANNEL_BINDING_FIELD_DESTINATION_TYPE_TYPE, | ||
| source: 'apilint', | ||
| message: "'destinationType' value must be a string", |
There was a problem hiding this comment.
should we be stricter with this rule since the description says? The type of destination, which MUST be either exchange or queue or fifo-queue
| documentation: { | ||
| kind: 'markdown', | ||
| value: | ||
| '[Schema object](https://www.asyncapi.com/docs/reference/specification/v2.6.0#schemaObject)\n\\\n\\\n**Optional**. A Schema object containing the definitions for Anypoint MQ-specific headers (so-called protocol headers). This schema MUST be of type `object` and have a `properties` key. Examples of Anypoint MQ protocol headers are `messageId` and `messageGroupId`.', |
There was a problem hiding this comment.
wrong version would be showed for other asyncapi specs :/
could you create an issue for supporting dynamic version?
There was a problem hiding this comment.
We can probably just add targetSpec and separate the rule for 3.0.
There was a problem hiding this comment.
yeap, we could, but we would have to do this also for async 3.1 soon even though the rule will be the same. 🤔
There was a problem hiding this comment.
I think that in general we use the latest spec for the major version, unless some fields have changed 🤔
For targeting minor versions - we probably need to go through each element to update them in that case 😔
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3 participants
This PR updates Anypoint MQ Bindings to version 0.1.0 and fixes missing version 0.0.1, wrong validation for the fields and validation not appearing for Server Bindings.