-
-
Notifications
You must be signed in to change notification settings - Fork 310
Description
Describe the bug.
When using request validation in the CLI, request body validation is skipped or reported as unsupported for certain paths or HTTP methods, even when a valid request body schema is defined for the operation.
As a result, invalid request bodies may pass validation without errors, or the CLI may indicate that validation is not supported, leading to incomplete or misleading validation results.
Expected behavior
If a request body schema is defined for an operation, the CLI should validate the request body against that schema for all supported paths and HTTP methods.
Invalid request bodies should consistently fail validation with clear and actionable error messages.
Screenshots
N/A – this is a validation logic issue and does not produce visual UI output.
How to Reproduce
- Create or use an AsyncAPI document with a defined request body schema.
- Select an operation that maps to a path or HTTP method currently reported as unsupported by the validator.
- Run the CLI request validation using a request body that violates the schema.
- Observe that validation is skipped or reported as unsupported instead of failing.
🖥️ Device Information [optional]
- Operating System (OS): Windows 10 / Linux / macOS
- AsyncAPI CLI version: latest
- Node.js version: 22.x
👀 Have you checked for similar open issues?
- I checked and didn't find similar issue
🏢 Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to work on this issue ?
Yes I am willing to submit a PR!
Metadata
Metadata
Assignees
Labels
Type
Projects
Status