@skyhook-io/radar-app 0.2.0 → 0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyhook-io/radar-app",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Radar's full web UI as a reusable React component. Used by Radar's own binary and by external consumers like Radar Cloud.",
   "repository": {
     "type": "git",

package/src/components/resources/ResourcesView.tsx

@@ -181,15 +181,14 @@ export function ResourcesView({ namespaces, selectedResource, onResourceClick, o
       pinned={pinned}
       togglePin={togglePin}
       isPinned={(kind: string, group?: string) => isPinned(kind, group ?? '')}
-      // Navigation. basePath is the full URL prefix where the Resources view
-      // lives — '/resources' for standalone Radar, '/c/{cluster}/resources'
-      // when embedded in a host app that mounts RadarApp under a basename.
-      // k8s-ui's ResourcesView uses this to read the current kind out of
-      // window.location.pathname and to write URL updates (drawer open/close,
-      // filter changes) back via history.replaceState. Without the basename
-      // prefix, those writes would drop the host-app route context and the
-      // URL would no longer be reloadable.
-      basePath={getBasename() + '/resources'}
+      // Navigation. basePath is basename-relative. React Router's useLocation
+      // strips the basename from `location.pathname`, so reading the current
+      // kind compares basename-relative paths on both sides. URL writes go
+      // through `handleNavigate`, which strips any leading basename before
+      // handing off to react-router (which re-applies it). Embedding hosts
+      // (e.g. Radar Cloud at /c/{cluster}/resources) work without ResourcesView
+      // needing to know the basename.
+      basePath="/resources"
       locationSearch={location.search}
       locationPathname={location.pathname}
       onNavigate={handleNavigate}