No AI provider is configured. Add a key in Settings › AI Keys before generating analyzers with AI.
Describe what your analyzer should detect in plain English. The AI will generate a JavaScript analyzer module that integrates with the existing analysis pipeline.
Good descriptions are specific:
controlTree — Unified tree of all controls in the app
screens[] — Array of screen nodescomponents[] — Array of component definitionsallNodes[] — Every control nodenodeIndex — Map<name, node>name, type, baseType, isScreen, isComponent, children[], formulas (Map), properties (Map), screen, filePathrefGraph — Cross-reference analysis
referencedControls — Map of which controls are referenced wherevariablesRead — Set of variable names that are consumedcollectionsRead — Set of collection names that are consumedextraction — Formula extraction results
allFormulas[] — Every formula with control, property, text, filevariableWrites — Map of Set/UpdateContext locationscollectionWrites — Map of Collect/ClearCollect locationsnavigateRefs — Map of Navigate() screen references
You can ask the analyzer to check anything the generated module can see in the app’s source:
controls and screens, Power Fx formulas, Set/UpdateContext variables,
Collect/ClearCollect collections, Navigate targets, component
definitions and instances, App.OnStart and App.Formulas, and cross-references
between them — so dead code, stale references, and pattern-based code-smell checks all work well.
What can I check? ›
Find every Button control where the OnSelect property is empty, only whitespace, the literal false, or just Select(Parent). For each hit, report the control's name, the screen it's on, the source file, and the offending formula snippet. Confidence should be high when OnSelect is empty/whitespace/false, and medium when it is Select(Parent).