Search templates, filters, and script constraints
When you construct a pattern for a structural search you are basically writing a script. To simplify your scripting process, IntelliJ IDEA offers you a list of predefined search templates that you can use as prototypes for your search pattern.
On how to access the list of the existing search and replace templates, see the structural search and replace section.
Each search or replace template consists of variables (
$variable_name$) to which you can add a condition (filter) to narrow your search results. Filters depend on a variable in your search template.
The Count filter specifies a number of occurrences.
For example, in the
new java.lang.RuntimeException($x$) search pattern, for
$x$ variable specify min and max numbers in the Count filter field.
[0,∞]to the variable and searches for the specified range of numbers.
The Reference filter references the variable in your search template.
The reference will always contain the name of a preconfigured or saved pattern, and you can use autocompletion to fill out this field.
For example, for the
$MethodCalls$ variable, type annotated methods in the Reference filter field.
IntelliJ IDEA searches for method calls to methods with annotations.
The Type filter adds a type of value or expression that is expected for the specified variable.
For example, for the
$expression$ variable, type
int in the Type filter field.
IntelliJ IDEA searches for places where boxing is performed for an integer.
The Text filter adds regular expressions or other text to the search pattern.
For example, you can search for classes that implement a certain interface. In this case, add a fully qualified name of the interface in the Text filter.
The Script filter adds Groovy script constraints to the search pattern. Script constraints are used when you search for certain language constructs.
For example, constructors with the specified number of parameters, or members with the specified visibility modifiers.
All variables used in a pattern can be accessed from script constraints. When you add a script constraint to your variable, IntelliJ IDEA matches it against the PSI tree, this variable is in fact a node in the PSI tree.
Let's say, you have a variable that matches a method, a
toString() method. Then this variable is actually a
PsiMethod node. Retrieving
variable.parent will produce a
PsiClass node, and so forth.
variable.text then will give you the entire text of the method. If you just need the name of the method, you can use
In another case the structural search and replace variable may match some expression, for example, a reference to a variable, a
PsiReferenceExpression. An expression has no name of course, but retrieving the entire text of the expression, will give you the name of the variable to which it is referring.
You can check the syntax of script constraints that are used in the following existing templates:
sample method invocation with a constant parameter
classes with parameterless constructors
static fields that are not final
interface that is not implemented or extended
fields/variables with given name pattern updated