Skip to content

Feature/6133 http route path parameters - #6383

Open
rohanranjan0902 wants to merge 3 commits into
clockworklabs:masterfrom
rohanranjan0902:feature/6133-http-route-path-parameters
Open

rohanranjan0902 wants to merge 3 commits into
clockworklabs:masterfrom
rohanranjan0902:feature/6133-http-route-path-parameters

Conversation

@rohanranjan0902

Copy link
Copy Markdown
Contributor

Description of Changes

Implements issue #6133 by adding dynamic HTTP route patterns across Rust, TypeScript, C++, and C#.

  • :name matches one non-empty path segment; for example, /items/:id matches /items/123.
  • A terminal * matches a non-empty path remainder, including additional slashes; for example, /webhooks/* matches /webhooks/provider/events.
  • Static routes take precedence over parameter routes, which take precedence over wildcards.
  • Route validation and conflict checks recognize malformed patterns and equivalent parameter shapes.
  • The matched path remains available through the existing request URI; the HTTP request ABI is unchanged.

API and ABI breaking changes

This is additive and does not change the HTTP request ABI.

Expected complexity level and risk

3/5. This changes route validation and dispatch across multiple language bindings and the shared schema. Route matching precedence and conflict detection need to stay consistent across those surfaces.

rohanranjan0902 and others added 3 commits September 24, 2026 22:46
…lockworklabs#5841)

When a previous test panics while compiling a module, the cache Mutex
becomes poisoned. This replaces .unwrap() with .unwrap_or_else() to
recover the lock, ensuring subsequent tests surface their actual
underlying errors rather than failing with a cascade of generic PoisonErrors.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant