[BUG] CLI fails for GitHub URLs with slash-based branches and multi-dot spec files

[akashcorex]

Describe the bug.

The CLI has two validation bugs causing valid inputs to fail.

1. GitHub URL Parsing

• Regex assumes branch names do not contain /
• Fails for valid URLs like:

https://github.com/org/repo/blob/feature/new-validation/spec.yaml

• Incorrect parsing leads to 404 errors

2. File Extension Detection

• Uses name.split('.')
• Fails for:

my.asyncapi.yaml
asyncapi

Expected Behavior

All valid GitHub URLs and specification files should be accepted.

Actual Behavior

Valid inputs are rejected or cause runtime failures.

Expected behavior

Expected behavior

The CLI should correctly accept and process:

• GitHub file URLs from any valid branch, including branches with slashes (e.g. feature/new-validation)
• Specification files with multiple dots in the filename (e.g. my.asyncapi.yaml)
• Filenames without extensions without crashing or behaving unpredictably

Valid inputs should not be rejected during validation.

Screenshots

Screenshots

N/A — this is a validation and parsing logic issue. The failure occurs during URL parsing and file validation, not in the UI.

How to Reproduce

How to reproduce

1. Run the CLI with a GitHub file URL from a branch containing a slash, for example:

   https://github.com/org/repo/blob/feature/new-validation/spec.yaml

2. Observe that the CLI fails due to incorrect branch parsing and returns a 404 error.
3. Run the CLI with a specification file named:

   my.asyncapi.yaml

4. Observe that the file is rejected due to incorrect extension detection.

🖥️ Device Information [optional]

• Operating System (OS):
• Browser:
• Browser Version:

👀 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 ?

None

[github-actions]

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.

[Varadraj75]

Hey @Shurtu-gal @Souvikns @AayushSaini101 ,
is this issue has been solved or can i work on it?

[ASHISH74888]

Hii @derberg @princerajpoot20 @Shurtu-gal ,
Is the issue still open? If so, I’d like to take it up.

[l8888888]

I've submitted a PR to fix both bugs mentioned in this issue: #2128

The PR addresses:

1. ✅ GitHub URL parsing for branch names with slashes (e.g., feature/new-validation)
2. ✅ File extension detection for multi-dot filenames (e.g., my.asyncapi.yaml)

Both issues are now resolved. Please review when you have a chance!

[BossChaos]

I'd like to work on this bug fix.

Plan:

1. Fix GitHub URL parsing regex to support branch names with slashes (e.g., feature/new-validation)
2. Fix file extension detection to handle multi-dot filenames (e.g., my.asyncapi.yaml)
3. Add test cases for both scenarios

ETA: Within 24 hours

Will submit PR once complete.

[BossChaos]

✅ Implementation Complete

I've submitted PR #2131 to fix this issue.

Changes:

1. Bug Fix: Updated regex pattern in validation.service.ts to support slash-based branch names (e.g., feature/new-validation)
2. Test Coverage: Added test case to validate the fix

Commits:

• 881ecda - fix: Support slash-based branches and multi-dot spec files
• e68e935 - test: Add test case for slash-based branch names

The PR is ready for review. Thanks! 🙏