skills.rest
tdcare
tdcareCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

salvo-path-syntax

Convert deprecated Salvo angle-bracket path parameters to curly-brace syntax.

1|Updated Mar 16, 2024
Search Tags:#routing#migration#syntax#salvo#path-parameters#version-compatibility
One-click install
npx skills add https://github.com/tdcare/genies --skill salvo-path-syntax-tdcare
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: salvo-path-syntax
Source: https://github.com/tdcare/genies/tree/main/.qoder/skills/salvo-path-syntax
Command: npx skills add https://github.com/tdcare/genies --skill salvo-path-syntax-tdcare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Path parameter syntax in Salvo has evolved from deprecated angle-bracket format to the current curly-brace syntax, requiring clear migration guidance for projects upgrading to newer versions.

Core Features & Use Cases

  • Migration guidance: Converts deprecated angle-bracket path parameters to curly-brace syntax across common patterns like basic params, typed params, regex constraints, and wildcards.
  • Version-aware guidance: Documents version-specific differences and ensures compatibility with Salvo 0.76+.
  • Practical examples: Provides concrete side-by-side comparisons to help developers migrate existing codebases with confidence.

Quick Start

Review your Salvo route definitions and replace all angle-bracket syntax with curly-brace syntax to align with 0.76+ routing.

Frequently Asked Questions about salvo-path-syntax

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Salvo path parameters from angle-bracket to curly-brace syntax?▼

To migrate Salvo path parameters, replace deprecated angle-bracket syntax in route definitions with the current curly-brace format. This ensures version compatibility and aligns routing patterns with Salvo 0.76+ expectations.

What is the correct syntax for typed params and regex constraints in Salvo 0.76+?▼

The correct syntax for typed params and regex constraints in Salvo 0.76+ uses curly-brace format. It replaces deprecated angle-brackets, applying version-aware guidance to maintain routing functionality across basic params, wildcards, and named wildcards.

Does Salvo still support angle-bracket wildcards in older project versions?▼

Salvo supports angle-bracket wildcards in deprecated older versions, but version-aware guidance enforces curly-brace syntax for 0.76+. Migration steps document side-by-side comparisons to transition basic params, typed params, and regex constraints confidently.

Why does my Salvo routing pattern break after upgrading to version 0.76?▼

Salvo routing patterns break after upgrading because path parameter syntax evolved from deprecated angle-bracket format to curly-brace syntax. You must apply migration guidance to update basic params, typed params, and wildcards for version compatibility.

What's the best way to convert deprecated Salvo wildcards to the current path syntax?▼

The best way to convert deprecated Salvo wildcards is applying version-aware migration guidance to replace angle-brackets with curly-brace syntax. This provides concrete steps and side-by-side examples illustrating correct syntax for 0.76+ routing.

Related Skills

Explore More Software Engineering Skills→
salvo-rssalvo-rs
20

salvo-path-syntax

Migrate Salvo route path parameters from angle-bracket to curly-brace syntax.

Official
Intermediate
salvo-rssalvo-rs
20

salvo-testing

Validate Salvo handlers, middleware, and routing with TestClient.

Official
Intermediate
salvo-rssalvo-rs
20

salvo-routing

Configure Salvo routing with nested routers, path parameters and filters.

Official
Advanced
harnessharness
80

migrate-pipeline

Migrate Harness pipelines from v0 to v1 via MCP tooling.

Official
Advanced