From 3ec55a86db3115f67e2a87a33a4e8bea95f126f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Tue, 9 May 2023 16:56:49 +0200 Subject: [PATCH] language_injection.md: clarify --- .../custom_language_support/language_injection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/reference_guide/custom_language_support/language_injection.md b/topics/reference_guide/custom_language_support/language_injection.md index bd3ccb79c..f66043166 100644 --- a/topics/reference_guide/custom_language_support/language_injection.md +++ b/topics/reference_guide/custom_language_support/language_injection.md @@ -99,7 +99,7 @@ The XML file with the injection configurations is loaded through the `org.intell It is important to make a distinction between plugin authors who want to provide injections into existing languages and plugin authors who want to provide support for IntelliLang injections in their custom language. Both define their injections by providing XML configurations and loading them through the [plugin.xml](plugin_configuration_file.md). However, custom language authors need to implement the `org.intellij.intelliLang.languageSupport` EP to make their language and PSI element patterns known to IntelliLang. -Therefore, plugin authors who want to provide injections for known languages can skip the first step. +Therefore, plugin authors who want to provide injections for existing languages can skip the first step. #### Implement org.intellij.intelliLang.languageSupport EP