class

Analyzer::Specification::CloudflareWrangler

Inherits Analyzer::Specification::SpecificationEngine < Analyzer < FileHelper < Reference < Object

Constants

METHOD_ANY = "ANY"

ROUTE_PATTERN_RE = /\A(?:[a-z][a-z0-9+.-]*:\/\/)?([^\/]+)(\/.*)?\z/i

A route pattern is [scheme://]<host><path> — example.com/api/*, *.example.com/*, https://example.com/api/*.

TOML_INLINE_TABLE_RE = /\{[^}]*\}/

TOML_PATTERN_RE = /(?:^|[\s{,])pattern\s*=\s*"([^"]+)"/m

Fallback for a wrangler.toml the TOML shard refuses. pattern = "..." only ever appears inside a routes entry in a wrangler config, so it can be scanned document-wide; the bare-string form has no such marker and is recovered from inside the routes = [ … ] array only.

TOML_ROUTES_ARRAY_RE = /^\s*routes\s*=\s*\[([^\]]*)\]/m

TOML_STRING_RE = /"([^"]+)"/

Class methods

tech_name

Source

Instance methods

analyze

Source

tech

Instance-side view of the same declaration. The per-file rescues live on this base class, which has no way to name the analyzer that is running inside them, so a skipped file could not be attributed to a tech. Deriving it from analyzer_for keeps the name written exactly once.

Source