fix regex related parsing route name

[ghg070]

We used swagger-typescript-api to parse and encountered the same issue as this developer (#532). Is it possible to modify the regex in parseRouteName to ensure that there is always a "/" or "..." at the beginning before treating it as a parameter?

[changeset-bot]

⚠️ No Changeset found

Latest commit: cb2ec8b

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

[Copilot]

Pull Request Overview

This PR fixes the regex in parseRouteName to ensure that only route parameters preceded by a "/" or "..." are matched.

• Updated regex in schema-routes.ts to use positive lookbehind for "/" or "..."
• Enhances route parameter parsing accuracy

Comments suppressed due to low confidence (1)

src/schema-routes/schema-routes.ts:101

• [nitpick] Consider adding an inline comment to explain the use of positive lookbehind in this regex, as this construct may be unfamiliar to some developers and can help maintainability.

      /(?<=\/|\.\.\.)({[\w[\\\]^`][-_.\w]*})|(?<=\/|\.\.\.)(:[\w[\\\]^`][-_.\w]*:?)/g,

[js2me]

Hello @ghg070
Please add some unit tests based on your changes