class

Analyzer::Dart::Angel3

Inherits Analyzer < FileHelper < Reference < Object

Angel3 (package:angel3_framework/angel3_framework.dart) is a full-featured, Express-style Dart server framework. Routes are registered against an Angel() instance with a method per verb:

var app = Angel(); app.get('/users', (req, res) => _listUsers(req)); app.post('/users', createUser); app.all('/health', (req, res) => 'ok');

Routes can be grouped under a shared prefix with group, whose second argument is a closure receiving a child router:

app.chain([cors()]).group('/api', (router) { router.get('/version', (req, res) => 'v0'); // GET /api/version });

group blocks nest, composing their prefixes. Path captures use the Express-style :id syntax, surfaced as {id} path params.

Routes are bound to variables holding an Angel() instance (or an Angel-typed parameter) and to the child-router parameter of a group closure, so calls on unrelated receivers (e.g. the package:http client's http.get(url)) are never mistaken for routes.

Not yet handled: reflection-based @Expose controller classes and the chain([...]).<verb>(...) form where the verb is called directly on a chain(...) result rather than a bound router variable.

Constants

ALL_VERBS = ["GET", "POST", "PUT", "PATCH", "DELETE", "HEAD", "OPTIONS"]
ANGEL_ASSIGN_REGEX = /(?:^|[;{}=(,\s])(?:final|var|const|late)\s+(?:Angel\s+)?([A-Za-z_]\w*)\s*=\s*(?:await\s+)?Angel\s*\(/

Variables holding an Angel() instance, plus parameters/fields typed Angel (so Future configureServer(Angel app) is picked up too).

ANGEL_TYPED_REGEX = /(?:^|[;{}(,])\s*Angel\s+([A-Za-z_]\w*)/
CALL_REGEX = /(?<![\w$.])([A-Za-z_]\w*)\s*\.\s*([a-zA-Z]+)\s*\(/

Receiver .verb( calls; (?<![\w$.]) keeps the receiver to a single identifier so chain([...]).post( (receiver is a )) is skipped.

GROUP_REGEX = /\.group\s*\(/
HTTP_METHOD_MAP = {"get" => "GET", "post" => "POST", "put" => "PUT", "patch" => "PATCH", "delete" => "DELETE", "head" => "HEAD", "options" => "OPTIONS"}

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

Nested types