for Windows and Linux
for macOS
Ctrl+Alt+S
Use this page to specify different names for the base-annotations to be used.
This helps avoid any dependencies on foreign code where it is not desired or possible. The custom annotations
should provide the same properties as the original ones, i.e. value for all of them and an optional
(default = "") prefix and suffix for the @Language replacement.
Also configure the runtime checks to be generated for the @Pattern validation.
| Item | Description |
|---|---|
| Annotation Classes |
In this area, specify the classes that implement annotations of the following types:
Type the class names, possibly using code completion. If necessary, use the Browse button
|
| Runtime Pattern Validation |
In this area, configure the runtime checks to be generated for the @Pattern validation. The available options are:
|
| Performance | Click one of the radio buttons in this area to select the level of analysis and performance of the language injections resolution procedure.
|
| Convert undefined operands to text in concatenation | If this check box is selected, IntelliJ IDEA inserts an injected operand as a literal, if its type is not recognized. |
| Add @Language annotation or comment if needed | This check box enables/disables adding annotations or comments. |
to open the