Websocket server online tester
pestsov-v opened this issue · 3 comments
Reason/Context
Please try answering few of those questions
- Why we need this improvement? - Userfrendly functionality
- How will this change help? - Add more popularity of community and create clear usefull experience
- What is the motivation? - Not to be a reader, but to be a tester.
Description
Please try answering few of those questions
- What changes have to be introduced? - Add the Websocket server online tester.
- Will this be a breaking change? - No. This is new feature.
- How could it be implemented/designed? -
- Add server instance which works into some host and port (may be add this paramaters to YAML / JSON configuration for servers block).
- This server instanse conevert this JSON schema object (documentation) end convert this to routines. This routines can be execute (like as SwaggerAPI).
- Add mock data block into parameters / payload and etc. Then this blocks are parse and implement into server routines. When documentator descripe event, then him can be execute routine with this fake (mock) data and tested this route.
P.S. This event driven server need to union base server url with event description.
This serve may be is killer fueture for your lib. Thanks for Attention.
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.
@pestsov-v hey thanks for the idea, I have some followup questions
Add server instance which works into some host and port
you mean basically host online somewhere app generated from this template. Like https://github.com/derberg/shrekapp-asyncapi-designed ?
This server instanse conevert this JSON schema object (documentation) end convert this to routines. This routines can be execute (like as SwaggerAPI).
I don't get what this JSON schema
are you referring to and what routines
you have in mind. Also not sure what are you referring to as SwaggerAPI
Add mock data block into parameters / payload and etc. Then this blocks are parse and implement into server routines. When documentator descripe event, then him can be execute routine with this fake (mock) data and tested this route
sorry don't get it
why is this needed, why not just use https://livepersoninc.github.io/ws-test-page/ and wss://ws.postman-echo.com/raw
This issue 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 issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue 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 issue forward. Connect with us through one of many communication channels we established here.
Thank you for your patience ❤️