@iloveagents/foundry-web-shell 0.1.0 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md ADDED
@@ -0,0 +1,38 @@
1
+ # @iloveagents/foundry-web-shell
2
+
3
+ ## 0.1.2
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies [30a4346]
8
+ - @iloveagents/foundry-agent@0.1.2
9
+ - @iloveagents/foundry-web-ui@0.1.2
10
+ - @iloveagents/foundry-web-primitives@0.1.2
11
+
12
+ ## 0.1.1
13
+
14
+ ### Patch Changes
15
+
16
+ - 689d3e9: feat(sidebar): distinct file-drop affordance for nav containers
17
+
18
+ `useNavItemDnd` now exposes `isFileDragOver` separately from `isDragOver`
19
+ so consuming nav items can render a prominent file-drop visual (dashed
20
+ primary outline + soft primary background + Upload icon) when the user
21
+ is dragging native files over the container. Previously file drags
22
+ shared the same subtle ring as entity-move drags, so users couldn't
23
+ tell that a folder accepted external files. Applies to all five nav-
24
+ item shapes (action-row leaf, button leaf, `NestedFolderItem`,
25
+ `CollapsibleNavItem` with children/actions, `NavLink` fallthrough) and
26
+ updates `ContainerDropZone` for visual parity.
27
+
28
+ Also fixes a related regression: the capture-phase
29
+ `onDragEnterCapture` / `onDragOverCapture` handlers were calling
30
+ `e.stopPropagation()`, which short-circuits React's synthetic dispatch
31
+ and prevented the bubble-phase `onDragEnter` (where state actually
32
+ mutates) from running. Removed — `preventDefault()` alone is enough to
33
+ mark the element as droppable.
34
+
35
+ - Updated dependencies [689d3e9]
36
+ - @iloveagents/foundry-web-ui@0.1.1
37
+ - @iloveagents/foundry-agent@0.1.1
38
+ - @iloveagents/foundry-web-primitives@0.1.1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@iloveagents/foundry-web-shell",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "license": "SEE LICENSE IN LICENSE",
5
5
  "type": "module",
6
6
  "types": "./src/index.ts",
@@ -17,9 +17,9 @@
17
17
  "@assistant-ui/react": "^0.12.25",
18
18
  "lucide-react": ">=0.400.0",
19
19
  "zustand": "^5.0.0",
20
- "@iloveagents/foundry-agent": "0.1.0",
21
- "@iloveagents/foundry-web-primitives": "0.1.0",
22
- "@iloveagents/foundry-web-ui": "0.1.0"
20
+ "@iloveagents/foundry-agent": "0.1.2",
21
+ "@iloveagents/foundry-web-primitives": "0.1.2",
22
+ "@iloveagents/foundry-web-ui": "0.1.2"
23
23
  },
24
24
  "devDependencies": {
25
25
  "typescript": "~5.9.3",
@@ -5,8 +5,13 @@ import { authStore } from "@iloveagents/foundry-agent/msal";
5
5
  * Default agent fetch client wired to the MSAL token store and the host's
6
6
  * Vite env. Customers can build their own via `createServiceFetch` from
7
7
  * `@iloveagents/foundry-agent` if they need different acquireToken / baseUrl behavior.
8
+ *
9
+ * Forward the optional ``{ forceRefresh }`` argument that the fetch
10
+ * interceptor passes on the 401 retry path. Without it, the retry would
11
+ * still ask MSAL for a cached token and the long-lived-tab 401 loop never
12
+ * recovers.
8
13
  */
9
14
  export const defaultAgentFetch: typeof fetch = createServiceFetch({
10
- acquireToken: () => authStore.getState().getAccessToken("api"),
15
+ acquireToken: (options) => authStore.getState().getAccessToken("api", options),
11
16
  baseUrl: import.meta.env.VITE_API_BASE_URL,
12
17
  });