fix: GitHub URL parsing and file extension detection for issue #1940

[597226617]

Description

This PR fixes two bugs reported in issue #1940:

Bug 1: GitHub URL Parsing with Slash-based Branch Names

Problem: The CLI failed to parse GitHub URLs when branch names contained slashes (e.g., feature/new-validation).

Root Cause: The regex pattern assumed branch names do not contain /:

const githubWebPattern = /^https:\/\/github\.com\/([^\/]+)\/([^\/]+)\/blob\/([^\/]+)\/(.+)$/;
//                                                                ^^^^^^^^
//                                                                Only matches non-slash characters

Fix: Updated the regex to capture the entire branch path (including slashes):

const githubWebPattern = /^https:\/\/github\.com\/([^\/]+)\/([^\/]+)\/blob\/(.+)\/([^\/]+)$/;
//                                                                ^^^^
//                                                                Matches any characters (including slashes)

Bug 2: File Extension Detection for Multi-dot Filenames

Problem: Files with multiple dots in the name (e.g., my.asyncapi.yaml) were incorrectly parsed.

Root Cause: Using name.split('.')[1] returns the second segment, not the extension:

'my.asyncapi.yaml'.split('.') // ['my', 'asyncapi', 'yaml']
//                               [1] = 'asyncapi' (WRONG!)

Fix: Use path.extname() which correctly handles multi-dot filenames:

const extension = path.extname(name).slice(1); // 'yaml' ✅

Testing

Both fixes have been tested with multiple test cases:

GitHub URL Parsing Tests

• ✅ https://github.com/org/repo/blob/feature/new-validation/spec.yaml
• ✅ https://github.com/org/repo/blob/main/spec.yaml
• ✅ https://github.com/org/repo/blob/feature/branch/name/spec.yaml

File Extension Tests

• ✅ asyncapi.yaml → yaml
• ✅ my.asyncapi.yaml → yaml
• ✅ test.v2.asyncapi.yaml → yaml
• ✅ file.with.many.dots.json → json

Related Issue

Closes #1940

[changeset-bot]

⚠️ No Changeset found

Latest commit: 481f690

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud