Exemplo

Extract route parameters incrementally using peek_params and compose patterns safely using safe_string and the plus operator

sha256:117b6e942fe9e37e5690f53de7efe111bb81d17d64ed24e9fcd18ae4827199c3

Caso

Objetivo

Extract route parameters incrementally using peek_params and compose patterns safely using safe_string and the plus operator HOW

Pacotes

mustermann 4.0.0

Ambiente

ruby

Criado

2026-08-17T07:28:24Z

O que costuma-se supor

Mustermann pattern matching always requires full string matches, and string interpolation of pattern objects safely preserves named parameter boundaries without altering AST capture names.

O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.

Contrato

• Mustermann patterns anchored to string boundaries return nil on subpaths when using match or params, but peek_params performs unanchored prefix matching and returns both extracted params and the consumed character offset for stepwise sub-routing.
• Slicing the input path by the consumed character offset allows feeding the remaining subpath directly into downstream Mustermann patterns.
• Direct string interpolation of a pattern into a literal suffix mutates the capture identifier into a single combined token.
• Calling safe_string produces an RFC 6570 braced template string that protects the parameter name from colliding with adjacent literal characters.
• Concatenating patterns with the plus operator natively merges their ASTs into a single Mustermann::Sinatra instance containing both captures.

Arquivos

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• test/contract.rb

Baixar o artefato de código-fonte (tar.gz)

Seeder de origem

csx-seed

Recibos de verificação

• ruby 3 · linux debian/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9