github.com/asyncapi/spec issues | Ecosyste.ms: OpenCollective

docs: add info about breaking changes to contributing guide

Dule-martins opened this pull request about 2 years ago

docs: set proper indentation for the TOC

smoya opened this pull request about 2 years ago

Channel parameter location inconsistency

jonaslagoni opened this issue about 2 years ago

feat: request/response support

GreenRover opened this pull request about 2 years ago

Work on 2.5.0 release

char0n opened this issue over 2 years ago

Unify all referencing mechanisms in v3

fmvilas opened this issue over 2 years ago

Clarify the shape of the SecurityRequirement Object

magicmatatjahu opened this issue over 2 years ago

docs: channel object / $ref note.

ponelat opened this pull request over 2 years ago

feat: introduce new schema referencing standard

jonaslagoni opened this pull request over 2 years ago

Creating the AsyncAPI Domain specification

fmvilas opened this issue over 2 years ago

[3.0.0] External docs/Contact as collection

magicmatatjahu opened this issue over 2 years ago

Proper STOMP Protocol Bindings

Crain-32 opened this issue over 2 years ago

[3.0.0] Allow references to be used in any part of the specification

magicmatatjahu opened this issue over 2 years ago

Linking AsyncAPI Spec to confluent Schema registry

realmohan001 opened this issue over 2 years ago

Kafka bindings - header - object type in header's json schema

oogetyboogety opened this issue over 2 years ago

feat!: release for version 3.0.0 of the spec

jonaslagoni opened this pull request over 2 years ago

chore: update release branch to 3.0

jonaslagoni opened this pull request over 2 years ago

Expanded tags support: allow adding tags to more entities, support refs

gabormagyar opened this issue over 2 years ago

Tool proposal for spec validation in Python / Pydantic

albertnadal opened this issue over 2 years ago

Ability to define a list of servers on which an operation is available

mgiovann opened this issue almost 3 years ago

Example Request: AMQP

lindhe opened this issue almost 3 years ago

Work on 2.4 release

smoya opened this issue almost 3 years ago

[Feature Request] Support $ref list in channels and components definition

TheLand opened this issue almost 3 years ago

Is there a way to document the guaranteed compatibility mode for produced messages?

thake opened this issue almost 3 years ago

Clarify usage or URN for an AsyncAPI spec id

thake opened this issue almost 3 years ago

Remove `$ref` field from `Channel Item Object` in next breaking change version (3.0.0)

char0n opened this issue almost 3 years ago

`example` is used for example for Schema Object examples (instead of `examples`)

aborg0 opened this issue almost 3 years ago

Introduce data format bindings

jessemenning opened this issue almost 3 years ago

Work on 3.0 release

jonaslagoni opened this issue almost 3 years ago

Remote and local servers

smoya opened this issue almost 3 years ago

What do we define as a breaking change?

jonaslagoni opened this issue almost 3 years ago

Should we have freeze period on release process?

magicmatatjahu opened this issue about 3 years ago

Let channels be identified by an ID rather than their address.

smoya opened this issue about 3 years ago

Which tools wants to stay up to date with the spec release?

jonaslagoni opened this issue about 3 years ago

Make `channels` field optional within an AsyncAPI file.

smoya opened this issue about 3 years ago

How do we define expected `schemaFormat` behavior in tooling?

jonaslagoni opened this issue about 3 years ago

A message header to signal deprecation

sdatspun2 opened this issue about 3 years ago

The many meanings of an AsyncAPI file

fmvilas opened this issue over 3 years ago

Proposal for Unparsable Remote References (mainly to support XML.)

damaru-inc opened this issue over 3 years ago

Proposal to introduce notion of environments

ekozynin opened this issue over 3 years ago

Proposal to allow defining schema format other than default one (AsyncAPI Schema)

magicmatatjahu opened this issue over 3 years ago

Proposal to solve publish/subscribe confusion

fmvilas opened this issue over 3 years ago

Proposal to be able to name channel item object

bali182 opened this issue over 3 years ago

Address perspective and channel reuse issues through introducing 'endpoint' concept

jessemenning opened this issue over 3 years ago

docs: update spec/asyncapi.md

vladdoster opened this pull request over 3 years ago

feat: request/response support in both operation and message objects

smarek opened this pull request over 3 years ago

should binding specs be tied to specific versions of the AsyncAPI spec?