# Intentions > For the complete documentation index, see [llms.txt](https://plugins.jetbrains.com/docs/intellij/llms.txt). > **TL;DR** > Product Help: [Intention Actions](https://www.jetbrains.com/help/idea/intention-actions.html) > > > > UI Guidelines: [Inspections](inspections.html) This topic describes the [conditional_operator_intention](https://github.com/JetBrains/intellij-sdk-code-samples/tree/main/conditional_operator_intention), a sample plugin that adds a new [intention action](https://www.jetbrains.com/help/idea/intention-actions.html) to the IDE Intentions list. In addition, the sample plugin contains a JUnit-based test. ## About Intention Actions The IntelliJ Platform analyzes the code and helps handle situations that may result in errors. When a possible problem is suspected, the IDE suggests an appropriate intention action, denoted with special icons. See the [Inspections](inspections.html) topic in UI Guidelines on naming, writing description, and message texts for inspections/intentions. You can view a list of all available intention actions as well as enable/disable them using the [Intentions List](https://www.jetbrains.com/help/idea/intention-actions.html#intention-settings) in `Settings | Editor | Intentions`. See the [Intention Action Preview](code-intentions-preview.html) topic on providing a preview of changes that can be made by executing an intention. ## Techniques Used The [conditional_operator_intention](https://github.com/JetBrains/intellij-sdk-code-samples/tree/main/conditional_operator_intention) sample plugin illustrates the use of the following techniques: * How to analyze a [PSI tree](psi-files.html). * How to find a Java token of interest in the PSI tree. * How to invoke a quick-fix action for a token element under the cursor using [PsiElementBaseIntentionAction](https://github.com/JetBrains/intellij-community/tree/idea/263.7307.200/platform/lang-api/src/com/intellij/codeInsight/intention/PsiElementBaseIntentionAction.java). * How to create a JUnit test for this plugin using [IdeaTestFixtureFactory](https://github.com/JetBrains/intellij-community/tree/idea/263.7307.200/platform/testFramework/src/com/intellij/testFramework/fixtures/IdeaTestFixtureFactory.java). * How to add an intention description and before/after examples in the Settings dialog > **Note:** > In the case of providing multiple intention actions for a single element, their ordering is indeterministic due to performance reasons. It is possible to push specific items up or down by implementing [HighPriorityAction](https://github.com/JetBrains/intellij-community/tree/idea/263.7307.200/platform/analysis-api/src/com/intellij/codeInsight/intention/HighPriorityAction.java) or [LowPriorityAction](https://github.com/JetBrains/intellij-community/tree/idea/263.7307.200/platform/analysis-api/src/com/intellij/codeInsight/intention/LowPriorityAction.java) respectively. ## Sample Plugin When launched, the sample plugin adds the SDK: Convert ternary operator to if statement item to the SDK intentions group in the `Settings | Editor | Intentions`. ### Running the Plugin See [Code Samples](code-samples.html) on how to set up and run the plugin. ### How does it work? The plugin analyzes symbols under the cursor in the code opened in the editor. If the cursor is positioned on the `?` conditional operator, IntelliJ IDEA proposes to replace this conditional (ternary) operator with the "if-then-else" statement: ![Convert ternary operator intention popup](images/ternary_operator_intention.png) Invoking SDK: Convert ternary operator to if statement intention action will result in transforming expression to the form visible in the [preview](code-intentions-preview.html) popup (code fragment on the right). ### Intention Description and examples The intention description is available in the UI in two places: * under `Settings | Editor | Intentions | SDK Intentions | SDK: Convert ternary operator to if statement`. * near the selected intention action in the [Context Actions](https://www.jetbrains.com/help/idea/intention-actions.html#apply-intention-actions) popup in the editor when [Preview](code-intentions-preview.html) cannot be shown. The before/after examples are available in the UI under `Settings | Editor | Intentions | SDK Intentions | SDK: Convert ternary operator to if statement`. The plugin provides description and before/after examples files in the `resources/intentionDescriptions/ConditionalOperatorConverter` directory: * `description.html` - provides the general information about the intention * `before.java.template` - shows the code fragment that intention can change * `after.java.template` - shows the code fragment after applying the intention By default, the intention description directory name is the same as the intention class name. It can be customized with the `` element in `` in `plugin.xml`. > **Warning:** > If intention class names are obfuscated in the [plugin distribution](plugin-content.html), always declare the `` element. "Before" and "after" filenames pattern is `before.$LANG_FILE_EXTENSION$.template` and `after.$LANG_FILE_EXTENSION$.template` respectively. If before/after preview is not needed, specify `true` in the `` in `plugin.xml`. > **Warning:** > If a plugin project is multi-module, and it combines resources into a single JAR, make sure that all intention description files have unique names or paths. Otherwise, only the last packed description file will exist in the distribution package. > **Tip:** > See the [Bundled Translations](providing-translations.html#bundled-translations) section for information about how to provide intention description translations in plugins. ### Testing the Plugin > **Note:** > Note that running the test requires setting system property `idea.home.path` in the `test` task configuration of the Gradle build script. The sample plugin contains the `ConditionalOperatorConverterTest` Java class and the test data in the `test/testData/` directory. To perform the plugin test, run the `ConditionalOperatorConverterTest.testIntention()` method.