From e311465a1e0d2d28ce0b98b8f1903fcba49d0bce Mon Sep 17 00:00:00 2001 From: Warren Buckley Date: Wed, 15 Feb 2023 09:06:31 +0000 Subject: [PATCH] Remove unused import --- .../libs/context-api/provide/context-provider.ts | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/Umbraco.Web.UI.Client/libs/context-api/provide/context-provider.ts b/src/Umbraco.Web.UI.Client/libs/context-api/provide/context-provider.ts index f9b1bfd189..c9ce3ab9c3 100644 --- a/src/Umbraco.Web.UI.Client/libs/context-api/provide/context-provider.ts +++ b/src/Umbraco.Web.UI.Client/libs/context-api/provide/context-provider.ts @@ -1,4 +1,3 @@ -import { map } from 'rxjs'; import { umbContextRequestEventType, isUmbContextRequestEvent, umbDebugContextEventType } from '../consume/context-request.event'; import { UmbContextToken } from '../context-token'; import { UmbContextProvideEventImplementation } from './context-provide.event'; @@ -72,6 +71,7 @@ export class UmbContextProvider { if(!event.instances){ event.instances = new Map(); } + // If the event doesn't have an instance for this context, add it. // Nearest to the DOM element of will be added first // as contexts can change/override deeper in the DOM @@ -80,7 +80,6 @@ export class UmbContextProvider { } }; - destroy(): void { // I want to make sure to call this, but for now it was too overwhelming to require the destroy method on context instances. (this.#instance as any).destroy?.();