use FQNs for EPs

This commit is contained in:
Yann Cébron 2019-12-03 15:23:04 +01:00
parent ce6d8b91d8
commit f98c6d66da
7 changed files with 10 additions and 12 deletions

View File

@ -22,7 +22,7 @@ When you access the index, you specify the key that you're interested in and get
A fairly simple file-based index implementation is the [UI Designer bound forms index](upsource:///plugins/ui-designer/src/com/intellij/uiDesigner/binding/FormClassIndex.java). Refer to it as an example to understand this topic better.
Each specific index implementation is a class extending [`FileBasedIndexExtension`](upsource:///platform/indexing-api/src/com/intellij/util/indexing/FileBasedIndexExtension.java). A file-based index should be registered in the `<fileBasedIndex>` extension point.
Each specific index implementation is a class extending [`FileBasedIndexExtension`](upsource:///platform/indexing-api/src/com/intellij/util/indexing/FileBasedIndexExtension.java). A file-based index should be registered in the `com.intellij.fileBasedIndex` extension point.
An implementation of a file-based index consists of the following main parts:

View File

@ -12,9 +12,9 @@ The *IntelliJ Platform* offers three types of services: _application level_ serv
To declare a service, you can use the following extension points in the IntelliJ Platform:
* `applicationService`: designed to declare an application level service.
* `projectService`: designed to declare a project level service.
* `moduleService`: designed to declare a module level service.
* `com.intellij.applicationService`: designed to declare an application level service.
* `com.intellij.projectService`: designed to declare a project level service.
* `com.intellij.moduleService`: designed to declare a module level service.
**To declare a service:**

View File

@ -65,7 +65,7 @@ Code formatting can be suppressed per region via [special comments](https://yout
To specify the default indent size for the language provided by your plugin, and to allow the user to configure the tab size and indent size you need to implement the
[`FileTypeIndentOptionsProvider`](upsource:///platform/lang-api/src/com/intellij/psi/codeStyle/FileTypeIndentOptionsProvider.java)
interface and to register the implementation in the `fileTypeIndentOptionsProvider` extension point.
interface and to register the implementation in the `com.intellij.fileTypeIndentOptionsProvider` extension point.
The return value of `createIndentOptions()` determines the default indent size.
### Rearranger

View File

@ -4,7 +4,7 @@ title: Documentation
To provide different kinds of documentation support (tooltips on **Ctrl-hover**, quick documentation popup etc.), the plugin needs to provide an implementation of the
[`DocumentationProvider`](upsource:///platform/analysis-api/src/com/intellij/lang/documentation/DocumentationProvider.java)
interface and register it in the `lang.documentationProvider` extension point.
interface and register it in the `com.intellij.lang.documentationProvider` extension point.
A standard base class for such implementations is available in the class
[`AbstractDocumentationProvider`](upsource:///platform/analysis-api/src/com/intellij/lang/documentation/AbstractDocumentationProvider.java).

View File

@ -14,7 +14,7 @@ public class DemoFramework extends FrameworkTypeEx {
```
## 2. Registering framework
The newly created framework class should be registered as an extension point by putting *framework.type* attribute into `<extensions>` section of the
The newly created framework class should be registered as an extension point by adding `com.intellij.framework.type` extension in
[plugin.xml](https://github.com/JetBrains/intellij-sdk-docs/blob/master/code_samples/framework_basics/src/main/resources/META-INF/plugin.xml)
configuration file:

View File

@ -14,7 +14,7 @@ to know how to do it.
## 1. Register Module Builder
Project configuration settings depend on the project's module type.
Register a new *moduleBuilder* extension point in the `plugin.xml` configuration file.
Register a new `com.intellij.moduleBuilder` extension point in the `plugin.xml` configuration file.
```xml

View File

@ -16,7 +16,7 @@ There are two main scenarios for the use of tool windows in a plugin.
In the first scenario (used by the Ant and Commander plugins, for example), a tool window button is always visible, and the user can activate it and interact with the plugin functionality at any time.
In the second scenario (used by the `Analyze Dependencies` action, for example), the tool window is created to show the results of a specific operation, and can be closed by the user after the operation is completed.
In the first scenario, the tool window is registered in *plugin.xml* using the `<toolWindow>` extension point.
In the first scenario, the tool window is registered in *plugin.xml* using the `com.intellij.toolWindow` extension point.
The extension point attributes specify all the data which is necessary to display the tool window button:
* The `id` of the tool window (corresponds to the text displayed on the tool window button)
@ -65,9 +65,7 @@ If closing tabs is enabled in general, you can disable closing of specific tabs
## How to Create a Tool Window?
The IntelliJ Platform provides the _toolWindow_ [extension point](/basics/plugin_structure/plugin_extensions_and_extension_points.md) that you can use to create and configure your custom tool windows. This extension point is declared using the [`ToolWindowEP`](upsource:///platform/platform-api/src/com/intellij/openapi/wm/ToolWindowEP.java) bean class.
To create a tool window, first declare an extension to the _toolWindow_ extension point.
The IntelliJ Platform provides the `com.intellij.toolWindow` [extension point](/basics/plugin_structure/plugin_extensions_and_extension_points.md) that you can use to create and configure your custom tool windows. This extension point is declared using the [`ToolWindowEP`](upsource:///platform/platform-api/src/com/intellij/openapi/wm/ToolWindowEP.java) bean class.
### Creation of Plugin