feat: let channels be identified by ID. Address is now moved into a new field #719
Conversation
|
Kudos, SonarCloud Quality Gate passed!
|
| @@ -20,13 +20,14 @@ These files can then be used to create utilities, such as documentation, integra | |||
| The file(s) MUST describe the operations an [application](#definitionsApplication) accepts. For instance, consider the following AsyncAPI definition snippet: | |||
|
|
|||
| ```yaml | |||
| user/signedup: | |||
| userSignedUp: | |||
| address: "user/signedup" | |||
There was a problem hiding this comment.
Perhaps we want to keep calling this path instead of address? I would love to know others opinion. I'm fine with address anyway.
smoya
changed the title
|
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 ❤️ |
|
Closing in favour of #827 |
This PR allows channels to be identified by an ID rather than by their address. Instead, the address has now been moved into a new field called
address.This is a breaking change so it should be considered as a candidate for
v3.0.0.Related issue(s):
See #663 for knowing about the reason behind this RFC.
CC @char0n @magicmatatjahu @derberg