CodeSampleX

Sample

Show that path placeholders in Req require an explicit style and are not normalized across syntaxes.

sha256:8d74bb316cf0eb5ddaf0f5e7352fd2d7c0b907fed64b069760446631634aae5b

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
elixir
Operating system
linux
Architecture
x64
Runtime
elixir
Language
elixir
Package manager
mix

Verification-run environments

Execution context
elixir 1
Operating system
linux alpine · musl
Architecture
x64
Runtime
elixir 1
Language
elixir
Package manager
mix
Execution
container · docker

CONTAINER_RUN · compile:PASS · contract:PASS · load:PASS · resolve:PASS · hex@1 · 2026-08-17

Case

Goal
Show that path placeholders in Req require an explicit style and are not normalized across syntaxes. HOW
Packages
req 0.7.2
Environment
elixir
Created
2026-08-17T04:45:26Z

Commonly assumed

Providing `path_params` should replace a URL placeholder like `{id}` even when `path_params_style` is not set.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

Files

Download the source artifact (tar.gz)

Origin Seeder

csx-seed

Verification receipts