Change "quick-fix" to "quick fix"

This is the actual feature name we use everywhere.
This commit is contained in:
Karol Lewandowski 2023-12-07 10:14:00 +01:00
parent 0f83aa773f
commit 7730473352
6 changed files with 6 additions and 6 deletions

View File

@ -6,7 +6,7 @@
Comparing References Inspection Sample demonstrates the implementation of the [Code Inspections][docs:code_inspections] feature for Java classes.
The plugin inspects your Java code and highlights any fragments containing the comparison of two `String` variables.
If such a check finds a comparison using the `==` or !`=` operators instead of the `.equals()` method, the plugin proposes a *quick-fix* action.
If such a check finds a comparison using the `==` or !`=` operators instead of the `.equals()` method, the plugin proposes a *quick fix* action.
### Extension Points

View File

@ -3,7 +3,7 @@
<body>
Reports usages of <code>==</code> and <code>!=</code> when comparing instances of String.
<p>
Quick-fix replaces operator with <code>equals()</code> call.
Quick fix replaces operator with <code>equals()</code> call.
</p>
</body>
</html>

View File

@ -43,6 +43,6 @@ A tutorial blog post series for JavaScript developers.
| **IntelliJ IDEA Conf 2021** <p>Various Speakers, 02/2021</p> <video src="https://www.youtube.com/watch?v=akrPpWAZzQk&amp;list=PLPZy-hmwOdEUdLO-AKiJJ7LuZ3p16zJ4x" title="IntelliJ IDEA Conf 2021" width="300"/> | <p>&nbsp;</p><p>Playlist includes a number of presentations related to plugin development</p> |
| **Busy Plugin Developers #0** <p>Mikhail Vink/Jakub Chrzanowski/Yann Cebron, 12/2020</p> <video src="https://www.youtube.com/watch?v=-6D5-xEaYig" title="Busy plugin developers series. Episode 0" width="300" /> | <p>&nbsp;</p><p>IntelliJ Platform Plugin Template</p><p>Plugin DevKit Features</p><p>IntelliJ Platform Explorer</p><p>What's coming in 2021?</p><p>Introduction to the Marketplace</p><p>How to make your plugin successful?</p><p>Sell on the Marketplace</p> |
| **How We Built Comma, the Raku IDE, on the IntelliJ Platform** <p>Jonathan Worthington, 01/2020</p> <video src="https://www.youtube.com/watch?v=zDP9uUMYrvs" title="How We Built Comma, the Raku IDE, on the IntelliJ Platform" width="300"/> | <p>&nbsp;</p><p>How to build custom language support</p><p>How to go from a language support plugin to an IDE</p><p>Lessons Learned</p><p>[Blog post](https://blog.jetbrains.com/platform/2020/01/webinar-recording-how-we-built-comma-the-raku-ide-on-the-intellij-platform/)</p> |
| **Building IntelliJ IDEA plugins in Scala** <p>Igal Tabachnik, 2020</p> <video src="https://www.youtube.com/watch?v=IPO-cY_giNA" title="Building IntelliJ IDEA plugins in Scala" width="300"/> | <p>&nbsp;</p><p>In this talk, I will show how to create plugins for IDEA from scratch in Scala, and show why Scala's unique features make it a great fit for such tasks as inspecting and manipulating Abstract Syntax Trees (ASTs) to create your own custom suggestions and quick-fixes.</p> |
| **Building IntelliJ IDEA plugins in Scala** <p>Igal Tabachnik, 2020</p> <video src="https://www.youtube.com/watch?v=IPO-cY_giNA" title="Building IntelliJ IDEA plugins in Scala" width="300"/> | <p>&nbsp;</p><p>In this talk, I will show how to create plugins for IDEA from scratch in Scala, and show why Scala's unique features make it a great fit for such tasks as inspecting and manipulating Abstract Syntax Trees (ASTs) to create your own custom suggestions and quick fixes.</p> |
| **Live Development of a PyCharm Plugin** <p>Joachim Ansorg, 2019</p> <video src="https://www.youtube.com/watch?v=cR-28eaXGQI" title="Live Development of a PyCharm Plugin" width="300"/> | <p>&nbsp;</p><p>Background and architecture of IntelliJ plugins</p><p>Development using tests</p><p>Implementing interesting extension points</p><p>Viewing the plugin in the IDE (PyCharm)</p><p>[Blog post](https://blog.jetbrains.com/pycharm/2019/01/webinar-recording-live-development-of-a-pycharm-plugin-with-joachim-ansorg/)</p> |
| **Build Developer Tools On Top of IntelliJ Platform** <p>Dmitry Jemerov, 2013</p> <video src="https://www.youtube.com/watch?v=vQDzjGzkPFc" title="Build Developer Tools On Top of IntelliJ Platform" width="300"/> | <p>&nbsp;</p><p>This webinar makes an overview on IntelliJ Platform and explains how you can use it for building your own products.</p> |

View File

@ -27,7 +27,7 @@ Custom language support provides basic functionality for working with a particul
* Syntax highlighting
* Formatting
* Code insight and code completion
* Inspections and quick-fixes
* Inspections and quick fixes
* Intention actions
Plugins can also augment existing (bundled) custom languages, e.g., by providing additional inspections, intentions, or any other features.

View File

@ -113,7 +113,7 @@ Within `DemoProjectSdkSetupValidator`:
* `isApplicableFor()` checks what condition(s) should be met to run the validation.
* `getErrorMessage()` runs the validation and return an appropriate error message if the validation fails.
* If the validation is successful, then it should return null.
* `getFixHandler()` returns an `EditorNotificationPanel.ActionHandler` that enables the user to execute a quick-fix to resolve the validation issue.
* `getFixHandler()` returns an `EditorNotificationPanel.ActionHandler` that enables the user to execute a quick fix to resolve the validation issue.
> `ProjectSdkSetupValidator` will not work in IntelliJ Platform-based IDEs such as PyCharm.

View File

@ -65,7 +65,7 @@ Please see [Grammar-Kit](https://github.com/JetBrains/Grammar-Kit) documentation
The grammar defines the flexibility of the support for a language.
The above grammar specifies that a property may have or may not have a key and value.
This flexibility allows the IntelliJ Platform to recognize incorrectly defined properties and provide corresponding code analysis and quick-fixes.
This flexibility allows the IntelliJ Platform to recognize incorrectly defined properties and provide corresponding code analysis and quick fixes.
Note that the `SimpleTypes` class in the `elementTypeHolderClass` attribute above specifies the name of a class that gets generated from the grammar in the scope of the <control>Generate Parser Code</control> action (see [](#generate-a-parser)); it doesn't exist at this point.