Contexts staying alive through navigation to content item where it is forbidden

patrickdemooij9 · March 17, 2025, 7:29am

I have a strange situation that I am not sure about if it is an Umbraco bug or something in my code. I have context X which is loaded on page A. This context observes the UMB_DOCUMENT_WORKSPACE_CONTEXT. I then navigate to page B which has a condition which prevents context X from loading, but the observe still triggers in that context resulting in my code loading some things in which it shouldn’t do.

Context in question is this one:

github.com/patrickdemooij9/SeoToolkit.Umbraco

main/src/SeoToolkit.Umbraco.MetaFields/assets/src/workspaces/MetaFieldsContentContext.ts

dev

import { UmbContextBase } from "@umbraco-cms/backoffice/class-api";
import {
  DocumentTypeValuePostViewModel,
  MetaFieldsSettingsViewModel,
} from "../api";
import { UmbWorkspaceContext } from "@umbraco-cms/backoffice/workspace";
import { UmbContextToken } from "@umbraco-cms/backoffice/context-api";
import { MetaFieldsContentRepository } from "../dataAccess/MetaFieldsContentRepository";
import { UmbControllerHost } from "@umbraco-cms/backoffice/controller-api";
import { UMB_DOCUMENT_WORKSPACE_CONTEXT } from "@umbraco-cms/backoffice/document";
import { UmbObjectState } from "@umbraco-cms/backoffice/observable-api";

interface MetaFieldsSettingsVariant {
  variant: string;
  model: UmbObjectState<MetaFieldsSettingsViewModel>;
  lastUpdated?: string | null;
}

export default class MetaFieldsContentContext
  extends UmbContextBase<DocumentTypeValuePostViewModel>

This file has been truncated. show original

And how I register it: