docs: provide reply definition #992
Conversation
Co-authored-by: Jonas Lagoni <[email protected]>
Co-authored-by: Jonas Lagoni <[email protected]>
…jects (asyncapi#796) Co-authored-by: Jonas Lagoni <[email protected]>
Co-authored-by: ue85540 <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
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.
|
@derberg as requested 😄 |
chore: update with master
…ply_definition # Conflicts: # spec/asyncapi.md
|
Change makes sense for me. |
Tenischev
requested review from
fmvilas,
derberg,
dalelane,
smoya,
char0n and
asyncapi-bot-eve
as code owners
…ition # Conflicts: # examples/adeo-kafka-request-reply-asyncapi.yml # scripts/converter/package-lock.json # scripts/converter/package.json # spec/asyncapi.md
|
There was a problem hiding this comment.
LGTM @Tenischev . Would you mind fixing the conflicts so I can +1 this?
|
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
title: "Provide more solid definition of the reply"
This PR adds definition of the reply message and fix a drift of naming response-reply in the spec.
Related issue(s):
Resolves: #980