struct

Noir::TreeSitterJvmLambdaDslExtractor::Config

Constructors

new(verb_methods : Hash(String, String), nest_methods : Set(String), handler_methods : Set(String) = Set(String).new, crud_methods : Set(String) = Set(String).new, transparent_methods : Set(String) = Set(String).new, query_methods : Set(String) = Set(String).new, form_methods : Set(String) = Set(String).new, header_methods : Set(String) = Set(String).new, cookie_methods : Set(String) = Set(String).new, body_methods : Set(String) = Set(String).new, body_typed_methods : Set(String) = Set(String).new, websocket_methods : Set(String) = Set(String).new, router_receivers : Set(String) = Set(String).new)

Source

Instance methods

body_methods

body_typed_methods

cookie_methods

crud_methods

form_methods

handler_methods

header_methods

nest_methods

query_methods

router_receivers

Receiver names (the object in recv.get(...)) that mark a verb call as a genuine route registration even when it carries no functional handler argument. Spark's redirect API (redirect.get("/from", "/to")) is the canonical case — its arguments are all string literals, so without an explicit allowlist it's indistinguishable from a colliding collection call like map.put("k", "v"). Matched against the receiver's last dotted segment, so both redirect.get(...) and Spark.redirect.get(...) resolve to redirect.

transparent_methods

verb_methods

websocket_methods