Inline event handler with multiple statements
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
An inline @event / v-on handler runs more than one statement (a semicolon followed by more code). Complex logic in the template is hard to read and test; move it into a method.
Why it matters
An inline handler that runs several statements puts real logic in the template, where it cannot be unit tested, reused, or read easily alongside the markup. As the handler grows it becomes a place bugs hide. This is a style heuristic, not a correctness bug, so it is low severity.
How to fix it
Move the handler body into a method (Options API) or a named function (Composition API) and reference it from the template: @click="handleThing". Keep the template calling a single named handler so the markup stays declarative and the logic stays testable.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo