Uh oh!
There was an error while loading. Please reload this page.
fix: complete MICROGRANT #2125 - URL parsing, file extensions, and request validation - #2128
Open
l8888888 wants to merge 3 commits into
Open
fix: complete MICROGRANT #2125 - URL parsing, file extensions, and request validation#2128l8888888 wants to merge 3 commits into
l8888888 wants to merge 3 commits into
Conversation
Fixesasyncapi#1940 This commit addresses two validation bugs in the CLI: 1. GitHub URL Parsing: - Previous regex assumed branch names don't contain '/' - Now correctly handles URLs like: https://github.com/org/repo/blob/feature/new-validation/spec.yaml - Parses branch and file path by working backwards from the filename 2. File Extension Detection: - Previous code used name.split('.')[1] which fails for: - Files with multiple dots (my.asyncapi.yaml) - Files without extensions (asyncapi) - Now uses .pop() to get the last segment after splitting by '.' - Properly handles undefined extensions Both fixes ensure valid inputs are no longer rejected.
l8888888
requested review from
AayushSaini101, Amzani, Shurtu-gal, Souvikns and asyncapi-bot-eve
as code ownersApril 21, 2026 16:59
🦋 Changeset detectedLatest commit: 81e75de The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide 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.
2 tasks
l8888888
commented
Apr 21, 2026
Author
Note about MICROGRANT #2125I noticed that #1940 is part of the MICROGRANT issue #2125, which also includes #1987. This PR currently fixes only #1940 (GitHub URL parsing and file extension bugs). Question for maintainers:
I'm happy to extend this PR to include both fixes if that's preferred. Please let me know! 🙏 |
Fixesasyncapi#1987 This commit fixes request body validation being skipped for certain paths or HTTP methods. Issues fixed: 1. Unsafe access to requestBody.content['application/json'] - Now uses optional chaining to safely check if content type exists - Prevents undefined access errors 2. Incorrect error when no requestBody schema is defined - Previously threw 'validation not supported' error - Now correctly skips validation when no schema is defined - This is valid behavior - not all endpoints require request bodies Changes: - Added safe access with optional chaining for content type - Changed validation logic to skip (not error) when no schema exists - Added clarifying comments Result: - Request body validation now works for all paths/methods - No false 'unsupported' errors for endpoints without request bodies - Invalid request bodies are properly validated when schema exists
This was referenced Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes#1940 and #1987 (Complete MICROGRANT #2125)
This PR addresses all bugs in the MICROGRANT issue #2125:
1. GitHub URL Parsing Bug (#1940)
Problem: The regex pattern assumed branch names don't contain
/, causing failures for valid URLs like:Solution: Rewrote the URL parsing logic to:
2. File Extension Detection Bug (#1940)
Problem: Used
name.split('.')[1]which fails for:my.asyncapi.yaml→ incorrectly gets "asyncapi" instead of "yaml"asyncapi→ undefined, causes crashSolution:
.pop()to get the last segment after splitting by.3. Request Body Validation Bug (#1987)
Problem: Request body validation was skipped or reported as "unsupported" for certain paths/methods, even when a valid schema was defined.
Root causes:
requestBody.content['application/json']caused undefined errorsSolution:
content?.['application/json'])Changes
src/domains/services/validation.service.ts: Updated GitHub URL parsing logicsrc/domains/models/SpecificationFile.ts: Fixed file extension detectionsrc/apps/api/middlewares/validation.middleware.ts: Fixed request body validation logicTesting
The fixes handle these cases correctly:
https://github.com/org/repo/blob/feature/new-validation/spec.yamlmy.asyncapi.yamlasyncapi(properly rejected as invalid)Checklist