class

Analyzer::Php::Yii

Inherits Analyzer::Php::PhpEngine < FileScanEngine < Analyzer < FileHelper < Reference < Object

Constants

MAX_RULE_GROUP_DEPTH = 16

GroupUrlRule nesting beyond this is not followed.

REST_ACTIONS = {"index" => ["GET"], "view" => ["GET"], "create" => ["POST"], "update" => ["PUT", "PATCH"], "delete" => ["DELETE"], "options" => ["OPTIONS"]}

Standard REST verbs auto-exposed by yii\rest\ActiveController.

REST_RULE_PATTERNS = {"PUT,PATCH {id}" => "update", "DELETE {id}" => "delete", "GET,HEAD {id}" => "view", "POST" => "create", "GET,HEAD" => "index", "{id}" => "options", "" => "options"}

yii\rest\UrlRule's default patterns. A verb-less entry matches any verb; it serves the options action.

REST_VERB_RE = /\A((?:(?:GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS),)*(?:GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS))(?:\s+(.*))?\z/

yii\rest\UrlRule pattern keys, where the pattern part is optional ('POST' => 'create').

RULE_VERB_RE = /\A((?:(?:GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS),)*(?:GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS))\s+(.+)\z/

A rule key that starts with a verb list, split the way yii\web\UrlManager::buildRules does: case-sensitive verbs, commas with no spaces, then whitespace and a pattern. Anything else ('get', 'POST') is a plain pattern.

RULES_KEY_RE = /["']rules["']\s*=>\s*(?:\[|array\s*\()/

Class methods

tech_name
Source

Instance methods

analyze_file(path : String) : Array(Endpoint)
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