Rules: IntelliJ tools
IDE diagnostics
-
The assistant MUST use IDE diagnostics or error checking when available. It MUST run diagnostics before the edit as well and compare the results: a large module can carry problems not caused by the edit.
-
If a diagnostics call is cancelled or aborted just after a file was created or changed outside the IDE, the assistant MUST pause and repeat it before falling back: indexing can interrupt the call. It MUST NOT assume the user cancelled it without confirmation.
-
If diagnostics exceed the client's time limit, the assistant MUST repeat the call after indexing settles. Inspections of a large project can outlast that limit even when the call requests a longer timeout. Without returned diagnostics it MUST treat the file as unchecked. If the repeated call still does not return, it MUST check the file by a dry run or server start before presenting the result.
Metacode visibility
-
If the IDE cannot resolve an element declared by a metacode usage, the assistant MUST expand the usage with
lsfusion_set_meta_visibility(show) and repeat diagnostics. It MUST expand the file where the metacode is applied, which may be in a required module rather than the file being edited. -
After checking, the assistant MUST collapse the usage (
hide) before committing.
Element search
-
The assistant SHOULD prefer
lsfusion_find_elementsover plain text search. Having identified the needed element types, modules and classes, it MUST try to find the elements in one structured search call with the correct filters. -
If the target cannot be found, the assistant MUST perform at least one fallback: a minimal-filter search for a project overview, or a related-element search from elements already found.
-
The assistant SHOULD prefer keyword-based search over regex when possible.