payload-nested-docs-page-tree 1.4.0 → 1.4.1

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 WLF Studios
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 WLF Studios
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,54 +1,54 @@
-# payload-nested-docs-page-tree
-
-Companion admin plugin for [`@payloadcms/plugin-nested-docs`](https://payloadcms.com/docs/plugins/nested-docs).
-
+# payload-nested-docs-page-tree
+
+Companion admin plugin for [`@payloadcms/plugin-nested-docs`](https://payloadcms.com/docs/plugins/nested-docs).
+
 <p align="center">
   <img alt="Page tree admin overview" src="assets/page-tree-admin-overview.png" width="100%" />
 </p>
-
+
 Adds a nested tree list view for nested docs collections in Payload admin, with visual hierarchy shading, live URL path previews, separate reorder and parent-move interactions, and status badges for published / changed / draft documents.
-
-It works alongside `@payloadcms/plugin-nested-docs`. It does not replace nested docs persistence, breadcrumbs generation, or routing.
-
-Tested with Payload `3.81` and Next.js `16.2`.
-
-
-## Install
-
-```bash
-pnpm add payload-nested-docs-page-tree
-```
-
-## Quick Setup
-
-`@payloadcms/plugin-nested-docs` should already be installed, and each target collection should already have:
-
-- a nested docs parent field
-- a nested docs breadcrumbs field
-- a top-level `admin.useAsTitle` field
-
-Add `nestedDocsPageTreePlugin(...)` right after `nestedDocsPlugin(...)`:
-
-```ts
-import { nestedDocsPlugin } from '@payloadcms/plugin-nested-docs'
-import { nestedDocsPageTreePlugin } from 'payload-nested-docs-page-tree'
-
-export const plugins = [
-  nestedDocsPlugin({
-    // your existing nested docs config
-  }),
-  nestedDocsPageTreePlugin({
-    collections: ['pages'],
-  }),
-]
-```
-
-Refresh the admin import map:
-
-```bash
-payload generate:importmap
-```
-
+
+It works alongside `@payloadcms/plugin-nested-docs`. It does not replace nested docs persistence, breadcrumbs generation, or routing.
+
+Tested with Payload `3.81` and Next.js `16.2`.
+
+
+## Install
+
+```bash
+pnpm add payload-nested-docs-page-tree
+```
+
+## Quick Setup
+
+`@payloadcms/plugin-nested-docs` should already be installed, and each target collection should already have:
+
+- a nested docs parent field
+- a nested docs breadcrumbs field
+- a top-level `admin.useAsTitle` field
+
+Add `nestedDocsPageTreePlugin(...)` right after `nestedDocsPlugin(...)`:
+
+```ts
+import { nestedDocsPlugin } from '@payloadcms/plugin-nested-docs'
+import { nestedDocsPageTreePlugin } from 'payload-nested-docs-page-tree'
+
+export const plugins = [
+  nestedDocsPlugin({
+    // your existing nested docs config
+  }),
+  nestedDocsPageTreePlugin({
+    collections: ['pages'],
+  }),
+]
+```
+
+Refresh the admin import map:
+
+```bash
+payload generate:importmap
+```
+
 ## What It Adds
 
 - replaces the collection list view with a nested tree table
@@ -87,58 +87,90 @@ Parent moves and orderable reordering are separate interactions.
 
 For collections using Payload `orderable`, the reorder handle is shown only when the current sort is the orderable field. Reordering only changes the order key and is limited to documents under the same parent, or documents at the root level. A reorder drag cannot change a document's parent.
 
-[Watch the orderable-only reorder handle demo](assets/orderable-reorder-handle.mp4)
+https://github.com/user-attachments/assets/b25ffa1a-a6bd-45cf-bce8-56ba6cdf7e72
+
+
 
 Parent moves are hidden by default because they change the page hierarchy. Editors can enable the parent-move handle with the `Edit Hierarchy` button when they intentionally want to move pages between parents. Drag a page onto another page to make it a child of that page. Drag it between root pages to move it back to the root level.
 
-[Watch the edit hierarchy mode demo](assets/edit-hierarchy-mode.mp4)
+Edit hierarchy mode
+
+https://github.com/user-attachments/assets/618d5e53-5918-40be-9932-0f516e5e82ba
+
+Parent move to child
+
+https://github.com/user-attachments/assets/4cb25109-e515-4955-8503-39fddac0020f
+
+Parent move back to root
+
+https://github.com/user-attachments/assets/470cb5b3-61c8-4b5b-a6e4-5e855f58a0e4
+
+Same-parent reorder guard
+
+https://github.com/user-attachments/assets/2513ff04-192e-4fdf-808f-6004f55d871c
 
-[Watch the parent move to child demo](assets/parent-move-to-child.mp4)
 
-[Watch the parent move back to root demo](assets/parent-move-to-root.mp4)
 
-[Watch the same-parent reorder guard demo](assets/reorder-same-parent-only.mp4)
 
 Internally, parent moves call this plugin's `/:id/move` endpoint. That endpoint updates the nested docs parent field through Payload's local API, while `@payloadcms/plugin-nested-docs` continues to own parent and breadcrumb behavior through its normal fields and hooks.
 
+### Publishing moves
+
+On a drafts-enabled collection a move is written through the drafts system, so by default it is staged as a **draft**: the tree updates immediately and the page shows a `changed` badge, but the live URL/path changes only when the page is next published. This is the safe default — publishing a move for a page that also has other pending edits would publish those edits too.
+
+Set `publishOnMove: true` to publish a move as soon as it happens — but only when it is safe to:
+
+```ts
+nestedDocsPageTreePlugin({
+  collections: ['pages'],
+  publishOnMove: true,
+})
+```
+
+With `publishOnMove` enabled, a move is published immediately **only if the moved page had no unpublished changes beforehand** (its latest version was already published). If the page has pending draft edits (a `changed` or draft-only page), the move stays staged exactly as before, so in-progress edits are never published as a side effect of a move. Collections without drafts always move live and are unaffected by this option.
+
+Publishing a move also republishes the moved page's descendants, so their live URLs follow the new parent. Since the live site really did change, a published move **does** trigger your deploy hook, once for the whole subtree - see [Deploy Hooks](#the-fix). Reorders and staged moves still do not. You do not need to change your hook when enabling this option.
+
+On a localized collection the parent field is shared across locales but breadcrumbs are not: publishing a move recomputes breadcrumbs only for the locale the move was made in, so other locales keep their previous URL until they are next published. If that matters for your setup, leave `publishOnMove` off.
+
 ## Home Indicator
 
 By default, the home icon is enabled only for the `pages` collection.
-
-```ts
-nestedDocsPageTreePlugin({
-  collections: ['pages'],
-})
-```
-
-For custom page collection slugs, pass an exact allow-list:
-
-```ts
-nestedDocsPageTreePlugin({
-  collections: ['page-tree', 'categories'],
-  homeIndicator: {
-    collections: ['page-tree'],
-  },
-})
-```
-
-To disable the home icon everywhere:
-
-```ts
-nestedDocsPageTreePlugin({
-  collections: ['pages'],
-  homeIndicator: false,
-})
-```
-
-## Status Badges
-
-The tree view supports three document states:
-
-- `published`: live and up to date
-- `changed`: live, but has unpublished changes
-- `draft`: not published
-
+
+```ts
+nestedDocsPageTreePlugin({
+  collections: ['pages'],
+})
+```
+
+For custom page collection slugs, pass an exact allow-list:
+
+```ts
+nestedDocsPageTreePlugin({
+  collections: ['page-tree', 'categories'],
+  homeIndicator: {
+    collections: ['page-tree'],
+  },
+})
+```
+
+To disable the home icon everywhere:
+
+```ts
+nestedDocsPageTreePlugin({
+  collections: ['pages'],
+  homeIndicator: false,
+})
+```
+
+## Status Badges
+
+The tree view supports three document states:
+
+- `published`: live and up to date
+- `changed`: live, but has unpublished changes
+- `draft`: not published
+
 Badge colors use Payload theme colors by default. To override badge labels or status colors, pass a `badges` object. Custom colors are treated as one base color per status and are adapted for both light and dark Payload themes:
 
 <p align="center">
@@ -147,40 +179,41 @@ Badge colors use Payload theme colors by default. To override badge labels or st
 
 ```ts
 nestedDocsPageTreePlugin({
-  collections: ['pages'],
-  badges: {
-    colors: {
-      // Example: use a custom green / blue / orange palette.
-      published: '#bbf3b0',
-      changed: '#b9eaf3',
-      draft: '#f8d5a7',
+  collections: ['pages'],
+  badges: {
+    colors: {
+      // Example: use a custom green / blue / orange palette.
+      published: '#bbf3b0',
+      changed: '#b9eaf3',
+      draft: '#f8d5a7',
     },
     labels: {
       // Example: use custom labels for states.
       published: 'Live',
       changed: 'Has Changes',
       draft: 'Draft Only',
-    },
-  },
-}),
-```
-
+    },
+  },
+}),
+```
+
 `labels` and `colors` are optional partial overrides. Missing entries fall back to the built-in Payload-themed defaults for published, changed, and draft states.
-
-## Configuration
-
-- `collections`: target collection slugs
-- `parentFieldSlug`: defaults to `'parent'`
-- `breadcrumbsFieldSlug`: defaults to `'breadcrumbs'`
-- `defaultLimit`: defaults to `100`
-- `hideBreadcrumbs`: defaults to `true`
-- `disabled`: defaults to `false`
-- `homeIndicator`: defaults to `{ collections: ['pages'] }`; set to `false` to disable
-- `badges`: optional label and color overrides for `published`, `changed`, and `draft`
-- `diagnostics`: defaults to `false`. Enables structured diagnostic logging for tree-related publish/draft regressions; see below.
-
-## Diagnostics Mode
-
+
+## Configuration
+
+- `collections`: target collection slugs
+- `parentFieldSlug`: defaults to `'parent'`
+- `breadcrumbsFieldSlug`: defaults to `'breadcrumbs'`
+- `defaultLimit`: defaults to `100`
+- `hideBreadcrumbs`: defaults to `true`
+- `disabled`: defaults to `false`
+- `homeIndicator`: defaults to `{ collections: ['pages'] }`; set to `false` to disable
+- `publishOnMove`: defaults to `false`. When `true`, a move is published immediately if the moved page had no unpublished changes; pages with pending edits stay staged. See [Publishing moves](#publishing-moves).
+- `badges`: optional label and color overrides for `published`, `changed`, and `draft`
+- `diagnostics`: defaults to `false`. Enables structured diagnostic logging for tree-related publish/draft regressions; see below.
+
+## Diagnostics Mode
+
 If a page-tree move or reorder is doing something unexpected, enable diagnostics and reproduce. Each page-tree-triggered write emits one or more structured events on the dev server stdout:
 
 <p align="center">
@@ -189,123 +222,135 @@ If a page-tree move or reorder is doing something unexpected, enable diagnostics
 
 ```ts
 nestedDocsPageTreePlugin({
-  collections: ['pages'],
-  diagnostics: true,
-})
-```
-
-Or with a custom sink:
-
-```ts
-nestedDocsPageTreePlugin({
-  collections: ['pages'],
-  diagnostics: {
-    enabled: true,
-    logger: (event) => req.payload.logger.info({ pageTree: event }),
-  },
-})
-```
-
+  collections: ['pages'],
+  diagnostics: true,
+})
+```
+
+Or with a custom sink:
+
+```ts
+nestedDocsPageTreePlugin({
+  collections: ['pages'],
+  diagnostics: {
+    enabled: true,
+    logger: (event) => req.payload.logger.info({ pageTree: event }),
+  },
+})
+```
+
 Each event is one line tagged `[payload-nested-docs-page-tree]` followed by the event source (`move-endpoint:enter`, `move-endpoint:ok`, `move-endpoint:error`, `reorder-endpoint:enter`, `reorder-endpoint:ok`, `reorder-endpoint:error`, `page-tree-change:after`, `page-tree-change:status-flip`) and a JSON payload that includes:
-
+
 - `flow`: id shared by every event for one logical operation
-- `publishedMainRowBefore` / `publishedMainRowAfter`: fresh reads of the public/published row (`draft: false`)
-- `before` / `after` / `changed`: projected diffs for `_status`, the parent field, and the orderable field when present
-
-If the published main row goes from `published` to anything else as a result of a page-tree change, the plugin additionally emits a `page-tree-change:status-flip` WARN line.
-
+- `publishedMainRowBefore` / `publishedMainRowAfter`: fresh reads of the public/published row (`draft: false`)
+- `before` / `after` / `changed`: projected diffs for `_status`, the parent field, and the orderable field when present
+
+If the published main row goes from `published` to anything else as a result of a page-tree change, the plugin additionally emits a `page-tree-change:status-flip` WARN line.
+
 Diagnostics is opt-in and adds extra reads per operation. Leave it off in production unless you are actively investigating.
-
-## Drag-And-Drop Is Triggering A Deploy?
-
-A drag-and-drop parent move calls `payload.update()` on the draft only. The published version of the live site is never touched. So in most setups, dragging a page does not trigger any rebuild and you can skip this section.
-
-### When you can skip this section
-
-- The default Payload website template on Vercel (or any host using Next.js ISR), with drafts and autosave on. The template's `afterChange` hook only calls `revalidatePath` and `revalidateTag` from `next/cache`. Those just clear the edge cache. They do not trigger a Vercel build, do not consume build minutes, and do not change what visitors see when the published HTML has not changed.
-- Any setup where your `afterChange` hooks only do in-process cache work (`revalidatePath`, `revalidateTag`, in-memory caches, etc.).
-
-### When you need the one-line fix
-
-You need the fix if **you** wrote an `afterChange` hook that calls something external or expensive on every save. Common cases:
-
-- **Cloudflare Pages / Netlify / Vercel Deploy Hooks** (`fetch(DEPLOY_HOOK_URL)`) - these trigger full rebuilds and burn build minutes.
-- **GitHub Actions** `repository_dispatch` triggers.
-- **Manually-invoked SSG rebuilds**.
-- **Publish notifications** (email, Slack) on status transitions.
-- **Heavy search reindex jobs** (Algolia, Meilisearch full-document push).
-
-Why a tree move trips these: a typical deploy hook fires when `previousDoc?._status === 'published'` so that it catches unpublish events too. A tree move on a published doc can match that condition, but the live site has not actually changed. Without the fix, every drag can fire your deploy.
-
-### The fix
-
-Add one line at the top of your hook. The plugin sets a flag on Payload's [hook context](https://payloadcms.com/docs/hooks/context) for every page-tree parent move, and your hook reads it to bail out early:
-
-```ts
-import { pageTreeMoveContextKey } from 'payload-nested-docs-page-tree'
-
-// at the top of your afterChange hook:
-if (req.context?.[pageTreeMoveContextKey]) return
-```
-
-This goes in **your** hook - the one that calls the deploy webhook. Not in any of the template's stock files.
-
-Full example:
-
-```ts
-import type { CollectionAfterChangeHook } from 'payload'
-
-import { pageTreeMoveContextKey } from 'payload-nested-docs-page-tree'
-
-export const triggerDeployOnPublishedChange: CollectionAfterChangeHook = async ({
-  doc,
-  previousDoc,
-  req,
-}) => {
-  // -- plugin opt-out --
-  if (req.context?.[pageTreeMoveContextKey]) return
-
-  // -- your deploy logic (example) --
-  // Fire on publish, republish, or unpublish - every transition the live site cares about.
-  if (doc._status === 'published' || previousDoc?._status === 'published') {
-    // POST to your Cloudflare / Netlify / Vercel deploy hook here
-  }
-}
-```
-
-See `dev/lib/rebuild.ts` for the full Cloudflare deploy hook example used by the dev playground.
-
-## Development
-
-For local plugin development, use the internal `dev/` app:
-
-```bash
-pnpm install
-pnpm dev
-pnpm generate:types
-pnpm generate:importmap
-```
-
-Plugin source is in `src/`. The internal test app is in `dev/`.
-
-For checks:
-
-```bash
-pnpm test:int
-pnpm exec tsc --noEmit
-```
-
-## Test in Another Project
-
-For release validation, test the packed artifact instead of a live source-folder dependency:
-
-```bash
-pnpm build
-pnpm pack
-```
-
-Then in the external consumer app:
-
-```bash
-pnpm add /path/payload-nested-docs-page-tree-*.tgz
-```
+
+## Drag-And-Drop Is Triggering A Deploy?
+
+A drag-and-drop parent move calls `payload.update()` on the draft only. The published version of the live site is never touched. So in most setups, dragging a page does not trigger any rebuild and you can skip this section.
+
+### When you can skip this section
+
+- The default Payload website template on Vercel (or any host using Next.js ISR), with drafts and autosave on. The template's `afterChange` hook only calls `revalidatePath` and `revalidateTag` from `next/cache`. Those just clear the edge cache. They do not trigger a Vercel build, do not consume build minutes, and do not change what visitors see when the published HTML has not changed.
+- Any setup where your `afterChange` hooks only do in-process cache work (`revalidatePath`, `revalidateTag`, in-memory caches, etc.).
+
+### When you need the one-line fix
+
+You need the fix if **you** wrote an `afterChange` hook that calls something external or expensive on every save. Common cases:
+
+- **Cloudflare Pages / Netlify / Vercel Deploy Hooks** (`fetch(DEPLOY_HOOK_URL)`) - these trigger full rebuilds and burn build minutes.
+- **GitHub Actions** `repository_dispatch` triggers.
+- **Manually-invoked SSG rebuilds**.
+- **Publish notifications** (email, Slack) on status transitions.
+- **Heavy search reindex jobs** (Algolia, Meilisearch full-document push).
+
+Why a tree move trips these: a typical deploy hook fires when `previousDoc?._status === 'published'` so that it catches unpublish events too. A tree move on a published doc can match that condition, but the live site has not actually changed. Without the fix, every drag can fire your deploy.
+
+### The fix
+
+Add one line at the top of your hook. The plugin sets a flag on Payload's [hook context](https://payloadcms.com/docs/hooks/context) for every page-tree write that leaves the live site unchanged, and your hook reads it to bail out early:
+
+```ts
+import { pageTreeMoveContextKey } from 'payload-nested-docs-page-tree'
+
+// at the top of your afterChange hook:
+if (req.context?.[pageTreeMoveContextKey]) return
+```
+
+The rule is simply **rebuild when the live site changed**, so this one line stays correct in every configuration:
+
+| What the editor did in the tree | Live site changed? | Your deploy hook |
+| --- | --- | --- |
+| Reordered siblings | no - only the order key was written | does not fire |
+| Moved a page, default settings | no - the move is staged as a draft | does not fire |
+| Moved a page with [`publishOnMove`](#publishing-moves) on | yes - the page and its descendants have new URLs | fires once |
+
+Only the last row publishes anything, which is why it is the only row that rebuilds. It fires once for the whole subtree, not once per descendant. Enabling `publishOnMove` needs no change to your hook - the same line already does the right thing.
+
+To rebuild after **every** page-tree drag, including reorders, just leave the guard out. That also rebuilds on staged moves, which change nothing live.
+
+This goes in **your** hook - the one that calls the deploy webhook. Not in any of the template's stock files.
+
+Full example:
+
+```ts
+import type { CollectionAfterChangeHook } from 'payload'
+
+import { pageTreeMoveContextKey } from 'payload-nested-docs-page-tree'
+
+export const triggerDeployOnPublishedChange: CollectionAfterChangeHook = async ({
+  doc,
+  previousDoc,
+  req,
+}) => {
+  // -- plugin opt-out --
+  if (req.context?.[pageTreeMoveContextKey]) return
+
+  // -- your deploy logic (example) --
+  // Fire on publish, republish, or unpublish - every transition the live site cares about.
+  if (doc._status === 'published' || previousDoc?._status === 'published') {
+    // POST to your Cloudflare / Netlify / Vercel deploy hook here
+  }
+}
+```
+
+See `dev/lib/rebuild.ts` for the full Cloudflare deploy hook example used by the dev playground.
+
+## Development
+
+For local plugin development, use the internal `dev/` app:
+
+```bash
+pnpm install
+pnpm dev
+pnpm generate:types
+pnpm generate:importmap
+```
+
+Plugin source is in `src/`. The internal test app is in `dev/`.
+
+For checks:
+
+```bash
+pnpm test:int
+pnpm exec tsc --noEmit
+```
+
+## Test in Another Project
+
+For release validation, test the packed artifact instead of a live source-folder dependency:
+
+```bash
+pnpm build
+pnpm pack
+```
+
+Then in the external consumer app:
+
+```bash
+pnpm add /path/payload-nested-docs-page-tree-*.tgz
+```

package/dist/components/PageTreeContext.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/components/PageTreeContext.tsx"],"sourcesContent":["'use client'\r\n\r\nimport type { DraggableAttributes, DraggableSyntheticListeners } from '@dnd-kit/core'\r\n\r\nimport React from 'react'\r\n\r\ntype PageTreeContextValue = {\r\n  activeDragRowID: null | string\r\n  canMoveDocs: boolean\r\n  collapsedIDs: ReadonlySet<string>\r\n  parentMoveEnabled: boolean\r\n  pendingMoveRowID: null | string\r\n  toggleRow: (rowID: string) => void\r\n}\r\n\r\ntype PageTreeRowDndContextValue = {\r\n  isOrderDragging: boolean\r\n  orderHandleAttributes: DraggableAttributes\r\n  orderHandleListeners: DraggableSyntheticListeners\r\n  orderHandleRef: (element: HTMLElement | null) => void\r\n}\r\n\r\nconst PageTreeContext = React.createContext<null | PageTreeContextValue>(null)\r\nconst PageTreeRowDndContext = React.createContext<null | PageTreeRowDndContextValue>(null)\r\n\r\nexport function PageTreeProvider({\r\n  children,\r\n  value,\r\n}: {\r\n  children: React.ReactNode\r\n  value: PageTreeContextValue\r\n}) {\r\n  return <PageTreeContext.Provider value={value}>{children}</PageTreeContext.Provider>\r\n}\r\n\r\nexport function PageTreeRowDndProvider({\r\n  children,\r\n  value,\r\n}: {\r\n  children: React.ReactNode\r\n  value: PageTreeRowDndContextValue\r\n}) {\r\n  return <PageTreeRowDndContext.Provider value={value}>{children}</PageTreeRowDndContext.Provider>\r\n}\r\n\r\nexport function usePageTree(): PageTreeContextValue {\r\n  const context = React.useContext(PageTreeContext)\r\n\r\n  if (!context) {\r\n    return {\r\n      activeDragRowID: null,\r\n      canMoveDocs: false,\r\n      collapsedIDs: new Set<string>(),\r\n      parentMoveEnabled: false,\r\n      pendingMoveRowID: null,\r\n      toggleRow: () => {},\r\n    }\r\n  }\r\n\r\n  return context\r\n}\r\n\r\nexport function usePageTreeRowDnd(): null | PageTreeRowDndContextValue {\r\n  return React.useContext(PageTreeRowDndContext)\r\n}\r\n"],"names":["React","PageTreeContext","createContext","PageTreeRowDndContext","PageTreeProvider","children","value","Provider","PageTreeRowDndProvider","usePageTree","context","useContext","activeDragRowID","canMoveDocs","collapsedIDs","Set","parentMoveEnabled","pendingMoveRowID","toggleRow","usePageTreeRowDnd"],"mappings":"AAAA;;AAIA,OAAOA,WAAW,QAAO;AAkBzB,MAAMC,gCAAkBD,MAAME,aAAa,CAA8B;AACzE,MAAMC,sCAAwBH,MAAME,aAAa,CAAoC;AAErF,OAAO,SAASE,iBAAiB,EAC/BC,QAAQ,EACRC,KAAK,EAIN;IACC,qBAAO,KAACL,gBAAgBM,QAAQ;QAACD,OAAOA;kBAAQD;;AAClD;AAEA,OAAO,SAASG,uBAAuB,EACrCH,QAAQ,EACRC,KAAK,EAIN;IACC,qBAAO,KAACH,sBAAsBI,QAAQ;QAACD,OAAOA;kBAAQD;;AACxD;AAEA,OAAO,SAASI;IACd,MAAMC,UAAUV,MAAMW,UAAU,CAACV;IAEjC,IAAI,CAACS,SAAS;QACZ,OAAO;YACLE,iBAAiB;YACjBC,aAAa;YACbC,cAAc,IAAIC;YAClBC,mBAAmB;YACnBC,kBAAkB;YAClBC,WAAW,KAAO;QACpB;IACF;IAEA,OAAOR;AACT;AAEA,OAAO,SAASS;IACd,OAAOnB,MAAMW,UAAU,CAACR;AAC1B"}
+{"version":3,"sources":["../../src/components/PageTreeContext.tsx"],"sourcesContent":["'use client'\n\nimport type { DraggableAttributes, DraggableSyntheticListeners } from '@dnd-kit/core'\n\nimport React from 'react'\n\ntype PageTreeContextValue = {\n  activeDragRowID: null | string\n  canMoveDocs: boolean\n  collapsedIDs: ReadonlySet<string>\n  parentMoveEnabled: boolean\n  pendingMoveRowID: null | string\n  toggleRow: (rowID: string) => void\n}\n\ntype PageTreeRowDndContextValue = {\n  isOrderDragging: boolean\n  orderHandleAttributes: DraggableAttributes\n  orderHandleListeners: DraggableSyntheticListeners\n  orderHandleRef: (element: HTMLElement | null) => void\n}\n\nconst PageTreeContext = React.createContext<null | PageTreeContextValue>(null)\nconst PageTreeRowDndContext = React.createContext<null | PageTreeRowDndContextValue>(null)\n\nexport function PageTreeProvider({\n  children,\n  value,\n}: {\n  children: React.ReactNode\n  value: PageTreeContextValue\n}) {\n  return <PageTreeContext.Provider value={value}>{children}</PageTreeContext.Provider>\n}\n\nexport function PageTreeRowDndProvider({\n  children,\n  value,\n}: {\n  children: React.ReactNode\n  value: PageTreeRowDndContextValue\n}) {\n  return <PageTreeRowDndContext.Provider value={value}>{children}</PageTreeRowDndContext.Provider>\n}\n\nexport function usePageTree(): PageTreeContextValue {\n  const context = React.useContext(PageTreeContext)\n\n  if (!context) {\n    return {\n      activeDragRowID: null,\n      canMoveDocs: false,\n      collapsedIDs: new Set<string>(),\n      parentMoveEnabled: false,\n      pendingMoveRowID: null,\n      toggleRow: () => {},\n    }\n  }\n\n  return context\n}\n\nexport function usePageTreeRowDnd(): null | PageTreeRowDndContextValue {\n  return React.useContext(PageTreeRowDndContext)\n}\n"],"names":["React","PageTreeContext","createContext","PageTreeRowDndContext","PageTreeProvider","children","value","Provider","PageTreeRowDndProvider","usePageTree","context","useContext","activeDragRowID","canMoveDocs","collapsedIDs","Set","parentMoveEnabled","pendingMoveRowID","toggleRow","usePageTreeRowDnd"],"mappings":"AAAA;;AAIA,OAAOA,WAAW,QAAO;AAkBzB,MAAMC,gCAAkBD,MAAME,aAAa,CAA8B;AACzE,MAAMC,sCAAwBH,MAAME,aAAa,CAAoC;AAErF,OAAO,SAASE,iBAAiB,EAC/BC,QAAQ,EACRC,KAAK,EAIN;IACC,qBAAO,KAACL,gBAAgBM,QAAQ;QAACD,OAAOA;kBAAQD;;AAClD;AAEA,OAAO,SAASG,uBAAuB,EACrCH,QAAQ,EACRC,KAAK,EAIN;IACC,qBAAO,KAACH,sBAAsBI,QAAQ;QAACD,OAAOA;kBAAQD;;AACxD;AAEA,OAAO,SAASI;IACd,MAAMC,UAAUV,MAAMW,UAAU,CAACV;IAEjC,IAAI,CAACS,SAAS;QACZ,OAAO;YACLE,iBAAiB;YACjBC,aAAa;YACbC,cAAc,IAAIC;YAClBC,mBAAmB;YACnBC,kBAAkB;YAClBC,WAAW,KAAO;QACpB;IACF;IAEA,OAAOR;AACT;AAEA,OAAO,SAASS;IACd,OAAOnB,MAAMW,UAAU,CAACR;AAC1B"}