Sample
Show how Router.mount handles an exact prefix, a trailing slash, and nested routes
sha256:6fe02156c65bb35677dd2ce10c035be187650275bc57c1dbfb9d6ef58449ba79
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- dart
- Operating system
- linux
- Architecture
- x64
- Runtime
- dart
- Language
- dart
- Package manager
- pub
Verification-run environments
- Execution context
- dart 3
- Operating system
- linux debian · glibc
- Architecture
- x64
- Runtime
- dart 3
- Language
- dart
- Package manager
- pub
- Execution
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · pub@1 · 2026-08-17
Case
- Goal
- Show how Router.mount handles an exact prefix, a trailing slash, and nested routes HOW
- Packages
-
shelf 1.4.2
shelf_router 1.1.4
- Environment
- dart
- Created
- 2026-08-17T03:53:45Z
Commonly assumed
Mounting with `'/api'` only handles `/api/...` and should not match a request to `/api` itself.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- A GET request to /api after app.mount('/api', subRouter.call) reaches the mounted sub-router root.
- A GET request to /api/user/alex reaches the mounted parameter route with name equal to alex.
- A GET request to /api/ reaches the same sub-router root route as /api.
Files
- NOTES.md
- csx.json
- pubspec.lock
- pubspec.yaml
- test/contract.dart
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- dart 3 · linux debian/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · pub@1 · 2026-08-17 · ed25519:d91480838ac982c9