comparison

boolean condition =
    i > 5;

Compares 2 expressions.

Configuration options

first

first configures the first part of the comparison, also called the left-hand side.

search:
    comparison:
        first:
            methodcall: {}
private static final int VALUE = 1;

boolean checkValue() {
    return getValue() == VALUE;
}

second

second configures the second part of the comparison, also called the right-hand side.

search:
    comparison:
        second:
            reference: {}
private static final int VALUE = 1;

boolean checkValue() {
    return getValue() == VALUE;
}

operator

A comparison operator that is one of the following:

  • ==

  • !=

  • >

  • >=

  • <

  • <=

search:
    comparison:
        operator: "!="
if (x == y &&
    y != z)
{
    // ...
}

Generic Configuration options

The following options are generic and available for every target.

anyOf

Similar to the logical operator OR: one or more descendant options should match.

search:
  <target>:
    anyOf:
    - name: "illegal"
    - name: "alsoIllegal"

allOf

Similar to the logical operator AND: all descendant options must match.

search:
  <target>:
    allOf:
    - annotation: "HttpPost"
    - annotation: "AllowUnAuthorized"

with

The only purpose to use this field is to make the recipe easier to read. It provides no additional functionality.

search:
  <target>:
    with:
      annotation: "HttpPost"

not, without

Works as the logical operator NOT. It will negate the result of the descendant options. Sensei presents the user with both options. They display the same behavior, but certain scenarios tend to read better using without.

search:
  <target>:
    not:
      annotation: "HttpPost"
search:
  <target>:
    without:
      annotation: "HttpPost"

in

Performs a structural search, this option is mainly used to narrow down recipes. Examples of this would be to only analyze and mark code inside a certain class or method that has a specific annotation. However, we haven't limited this option to only support these two scenarios. More advanced configuration can be achieved.

search:
  <target>:
    in:
      class:
        name:
          contains: "Controller"
search:
  <target>:
    in:
      method:
        annotation:
          type: "HttpPost"