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

WebSocket AsyncAPI generation #6667

Closed
4 tasks done
Bhashinee opened this issue Jun 27, 2024 · 1 comment
Closed
4 tasks done

WebSocket AsyncAPI generation #6667

Bhashinee opened this issue Jun 27, 2024 · 1 comment

Comments

@Bhashinee
Copy link
Member

Bhashinee commented Jun 27, 2024

Description:
This is to track the improvements that we need to make for the current implementation.

  • [1] Need to move the pipe code to the WebSocket module and use it in the client generation.
  • [2] Remove doc warnings of the generated client.
  • [3] Dispatcher stream id - When dispatcherStreamId is a required field, the user needs to provide a dummy value for it before the client replaces it with the actual value. The solution that we came across was to have an open record without the dispatcher stream ID field if it is present in the AsyncAPI spec.
  • Implement dispatcher stream id in the WebSocket protocol. (Implement dispatcher stream id in the WebSocket protocol. #6757)
@Bhashinee
Copy link
Member Author

We are not going to implement the first one as it was discussed to add the pipe module as a library.
Dispatcher streamID is implemented in ballerina-platform/module-ballerina-websocket#1367

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants