Skip to content

fix: place Cascadia Technology node at root of Management Client tree - #20

Merged
joshooaj merged 1 commit into
mainfrom
fix/19-admin-tree-hierarchy
Aug 3, 2026
Merged

joshooaj merged 1 commit into
mainfrom
fix/19-admin-tree-hierarchy

Conversation

@joshooaj

@joshooaj joshooaj commented Aug 3, 2026

Copy link
Copy Markdown
Owner

Summary

Fixes #19 — the Management Client site navigation tree hierarchy regression.

The plugin's admin content appeared in the wrong places: "Web Content Workspaces" was a root-level parent node (sibling of Site/Cameras/MIP Plug-ins), and "Cascadia Technology" was an empty node under the generic "MIP Plug-ins" root.

Changes

src/WebContent/WebContentPluginDefinition.cs (2 lines):

  • AdminPlacementHint Default -> Root — the "Cascadia Technology" shared node now sits directly under the tree root instead of under "MIP Plug-ins".
  • ItemNode trailing PlacementHint.Root -> PlacementHint.Default — "Web Content Workspaces" now nests under the shared node instead of appearing as a root sibling.

Verification

  • Enum semantics confirmed against MilestoneSystems.VideoOS.Platform 26.1.2 assembly (AdminPlacementHint.Root places the shared node under the tree root; PlacementHint.Default nests the item node under the plugin's shared node) and the official AdminMultiTab/ConfigDump samples.
  • Build: full MSBuild succeeds (WebContent.dll produced).
  • Tests: WebContent.Tests 14/14 pass (no SDK-bound seam was testable in the net8 test project).
  • Reviewed via /code-review against main: Standards (no violations/smells) and Spec (faithful match to ticket) both clean.

Out of scope (per ticket)

Renaming nodes/icons, Smart Client behavior, wiring up the root-node user control, license/security actions.

Fix the Management Client site navigation hierarchy so the plugin's
shared node ("Cascadia Technology") sits directly under the tree root
and the "Web Content Workspaces" item node nests under it, instead of
the item node appearing at the root with an empty shared node under
"MIP Plug-ins".

Set AdminPlacementHint.Root for the plugin-level shared node placement
and fall back to PlacementHint.Default for the workspace ItemNode so it
belongs under the shared node. Closes #19.
@joshooaj
joshooaj merged commit a062fdd into main Aug 3, 2026
1 check passed
@joshooaj
joshooaj deleted the fix/19-admin-tree-hierarchy branch August 3, 2026 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Management Client tree node hierarchy is broken

1 participant