@easyteam/auto-scheduler-modal-ui 0.1.0

package/LICENSE.txt

@@ -0,0 +1,3 @@
+Copyright (c) EasyTeam
+
+All rights reserved.

package/README.md

@@ -0,0 +1,87 @@
+# @easyteam/auto-scheduler-modal-ui
+
+Standalone React modal component for configuring auto-scheduler options.
+
+## Install
+
+```bash
+# npm
+npm i @easyteam/auto-scheduler-modal-ui
+
+# yarn
+yarn add @easyteam/auto-scheduler-modal-ui
+```
+
+## Usage
+
+```tsx
+import { AutoSchedulerModalWithProvider } from "@easyteam/auto-scheduler-modal-ui";
+
+const jurisdictions = [
+  {
+    id: "paga",
+    title: "California (PAGA)",
+    locations: [
+      { id: "sf-hq", name: "San Francisco HQ" },
+      { id: "oakland", name: "Oakland Warehouse" },
+    ],
+  },
+  {
+    id: "nyll",
+    title: "New York (NYLL)",
+    locations: [
+      { id: "brooklyn", name: "Brooklyn Office" },
+      { id: "manhattan", name: "Manhattan Store" },
+    ],
+  },
+];
+
+const themeOverride = {
+  tokens: {
+    colors: {
+      brand: {
+        500: "#303030",
+      },
+    },
+  },
+  autoSchedulerModal: {
+    banner: { bg: "#f2f9f6" },
+    primaryButton: { bg: "#1f2937" },
+  },
+};
+
+<AutoSchedulerModalWithProvider
+  isOpen={isOpen}
+  onClose={() => setOpen(false)}
+  title="Auto-scheduling"
+  jurisdictions={jurisdictions}
+  selectedLocationIds={selectedLocationIds}
+  onSelectedLocationIdsChange={setSelectedLocationIds}
+  theme={themeOverride}
+/>;
+```
+
+`AutoSchedulerModalWithProvider` bundles its own `ChakraProvider`, so you don't need to wrap it yourself. This avoids "Cannot read properties of null (reading 'useContext')" errors that can occur when the host app has multiple React instances (e.g. local packages in Next.js).
+
+If your app already provides a `ChakraProvider`, you can use the bare `AutoSchedulerModal` import instead.
+
+## Props
+
+The component is fully controlled and exposes typed props for:
+
+- modal open/close
+- jurisdictions + selected locations
+- primary/cancel labels
+- optional theme overrides
+- hard constraints dropdown with internal numeric inputs
+
+### Theme prop
+
+The `theme` prop accepts either:
+
+- EasyTeam-style overrides: `{ tokens?: { colors?: ... }, ...componentOverrides }`
+- Chakra v2 `ThemeOverride`
+
+When provided, the component merges the override into the active Chakra theme and wraps itself in a nested `ChakraProvider` to scope the overrides.
+
+See `AutoSchedulerModalProps` for full type definitions.