Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Operations object should have function channel() instead of channels() #120

Open
2 tasks done
snailtomatoes opened this issue Aug 28, 2024 · 1 comment
Open
2 tasks done
Labels
bug Something isn't working

Comments

@snailtomatoes
Copy link

Describe the bug.

As per spec v3.0.0 Operations are unique and only support a single Channel. Doesn't make much sense to return a Channels object since it should only contain only one Channel.

https://www.asyncapi.com/docs/reference/specification/v3.0.0#operationObject
https://github.com/asyncapi/parser-api/blob/master/docs/api.md

Expected behavior

parser should support operation.channel() and not operation.channels()

Screenshots

How to Reproduce

🥦 Browser

None

👀 Have you checked for similar open issues?

  • I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

Are you willing to work on this issue ?

None

@snailtomatoes snailtomatoes added the bug Something isn't working label Aug 28, 2024
Copy link

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant