From 1c0c187d6ac9fe6eef4ebbc70fcf1562ea647a79 Mon Sep 17 00:00:00 2001 From: Camila Belo Date: Tue, 16 Jan 2024 13:01:33 +0100 Subject: [PATCH] Update docs/frontend-system/architecture/05-extension-overrides.md Co-authored-by: Philipp Hugenroth Signed-off-by: Camila Belo --- docs/frontend-system/architecture/05-extension-overrides.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/frontend-system/architecture/05-extension-overrides.md b/docs/frontend-system/architecture/05-extension-overrides.md index ffe8ff11c4..6921315d5a 100644 --- a/docs/frontend-system/architecture/05-extension-overrides.md +++ b/docs/frontend-system/architecture/05-extension-overrides.md @@ -79,7 +79,7 @@ If the plugin you want to change is internal to your company or you just want to Note that it can still be a good idea to split your overrides out into separate packages in large projects. But it's up to you to decide how to group the extensions into extension overrides. -## Overriding Plugin Extensions +## Override Plugin Extensions To override an extension that is provided by a plugin, you need to provide a new extension that has the same ID as the existing extension. That is, all kind, namespace, and name options must match the extension you want to replace. This means that you typically need to provide an explicit `namespace` when overriding extensions from a plugin.