class

Analyzer::Rust::Dioxus

Inherits Analyzer::Rust::Leptos < Analyzer::Rust::RustEngine < FileScanEngine < Analyzer < FileHelper < Reference < Object

Dioxus fullstack server functions. #[server] takes the same arguments as Leptos's (Dioxus parses them with the server_fn argument grammar) but defaults to a JSON body. Dioxus 0.7 adds #[get("/path/{id}?q&r")] and its siblings: the literal is an axum path plus the query fields, and every function argument not bound by the path or the query travels in the JSON body. Arguments after the literal (auth: Session) are server-side extractors, not client input.

Constants

PATH_CAPTURE_RE = /\{\*?(\w+)\}|(?:^|\/)[:*](\w+)/
VERB_ATTR_RE = /#\s*\[\s*(?:\w+\s*::\s*)*(?:server|get|post|put|delete|patch)\b/
VERBS = Set {"get", "post", "put", "delete", "patch"}

Class methods

tech_name
Source

Instance methods

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