@feedmepos/mf-hrm-portal 2.2.5-dev.9 → 2.3.0-dev

package/dist/src/views/scheduling/schedule-store.d.ts

@@ -1,53 +1,10 @@
 import type { IFdtoPosUserSummary } from '@/types/employee';
-import type { FdtoScheduleAssignment, FdtoScheduleAutoScheduleReq, FdtoScheduleAutoScheduleResult, FdtoScheduleBoard, FdtoScheduleBulkUpdateAssignmentStatusReq, FdtoScheduleCreateEmployeeProfileReq, FdtoScheduleSaveAssignmentReq, FdtoScheduleSavePositionReq, FdtoScheduleSaveScheduleDayReq, FdtoScheduleUpdateEmployeeProfileReq, ScheduleReplaceDemandReq } from '@/types/schedule';
+import type { FdtoScheduleAssignment, FdtoScheduleAutoScheduleApplyReq, FdtoScheduleAutoScheduleApplyResult, FdtoScheduleAutoScheduleCapabilities, FdtoScheduleAutoScheduleGenerateReq, FdtoScheduleAutoScheduleResult, FdtoScheduleBulkUpdateAssignmentStatusReq, FdtoScheduleCreateEmployeeProfileReq, FdtoScheduleSaveAssignmentReq, FdtoScheduleSavePositionReq, FdtoScheduleSaveScheduleDayReq, FdtoScheduleUpdateEmployeeProfileReq, FdtoScheduleCreateTimeOffReq, FdtoScheduleTimeOff, FdtoScheduleUpdateTimeOffStatusReq, FdtoScheduleSaveEmployeeConfigsReq, ScheduleReplaceDemandReq } from '@/types/schedule';
+export { businessEmployees, dataVersion, employeeOutletIds, loadError, loading, outletId, payload, restaurantEmployees, employeeConfigs, rosterLoading, scheduleSetupCompleted, } from './schedule-state';
 /** dayjs-free local-date key — the board's own isoDateKey, repeated here so the store does not
  * have to import a composable. Local Y/M/D, never UTC: a BSON-free 'YYYY-MM-DD' that survives
  * a timezone west of Greenwich. */
 export declare function isoDate(d: Date): string;
-export declare const payload: import("vue").ShallowRef<FdtoScheduleBoard | null, FdtoScheduleBoard | null>;
-export declare const loading: import("vue").Ref<boolean, boolean>;
-/** The POS roster (who the board's rows are) is fetched separately from the board window. */
-export declare const rosterLoading: import("vue").Ref<boolean, boolean>;
-export declare const loadError: import("vue").Ref<string | null, string | null>;
-/** Whether this outlet has finished setting up scheduling (onboarding). The schedule settings
- * will carry this, but the backend has no such field yet, so it is a plain flag that defaults to
- * "not finished" — the setup banner keys off it. TODO: when the field exists, set it from the
- * settings payload where `payload` is applied (and flip it when the onboarding wizard finishes);
- * nothing else needs to change. */
-export declare const scheduleSetupCompleted: import("vue").Ref<boolean, boolean>;
-/** Bumped every time `payload` is replaced. Anything that caches a derived view of the data
- * — the board's per-week buckets above all — watches this and rebuilds. */
-export declare const dataVersion: import("vue").Ref<number, number>;
-/** The outlet the board is reading. A ref rather than a plain variable so the picker's label
- * follows a switch immediately, without waiting for the new outlet's payload to land. */
-export declare const outletId: import("vue").Ref<string, string>;
-/** Who actually works this outlet, per the POS roster (`restaurantRole` on the pos-user
- * record) — the board's roster is everyone here, not everyone with a Schedule EmployeeProfile.
- * A profile stays business-wide scheduling settings for a person (pay/positions/availability);
- * it no longer decides who shows up at all, only what shows once they do. */
-export declare const restaurantEmployees: import("vue").Ref<{
-    _id: string;
-    name: string;
-    code?: string | undefined;
-    passcode: string;
-    isMasterUser: boolean;
-    isRestricted: boolean;
-    restaurantRole: {
-        restaurantId: string;
-        roleId: string;
-    }[];
-}[], IFdtoPosUserSummary[] | {
-    _id: string;
-    name: string;
-    code?: string | undefined;
-    passcode: string;
-    isMasterUser: boolean;
-    isRestricted: boolean;
-    restaurantRole: {
-        restaurantId: string;
-        roleId: string;
-    }[];
-}[]>;
 /** Points the board at an outlet. Switching throws the held window away rather than widening
  * it — two outlets' rosters are not one dataset, and half of each is not a schedule.
  *
@@ -61,25 +18,21 @@ export declare function setOutlet(restaurantId: string): boolean;
  * separate invalidation path. A generous page size rather than looping pages: real restaurant
  * headcounts sit nowhere near it. */
 export declare function ensureRestaurantEmployeesLoaded(restaurantId: string): Promise<void>;
+export declare function saveEmployeeConfigs(configs: FdtoScheduleSaveEmployeeConfigsReq['configs']): Promise<void>;
+export declare function setEmployeeSchedulingEnabled(employeeId: string, enabled: boolean): Promise<void>;
 /** Re-reads this outlet's POS roster. The roster is what the board's rows are built from and is
  * otherwise fetched once per outlet, so any write that changes who works here (add, remove)
  * has to call this for the grid to show it. */
 export declare function refreshRestaurantEmployees(): Promise<void>;
 /** Gives an existing POS user a role at this outlet, so they land on its roster. */
 export declare function addEmployeeToOutlet(employeeId: string, roleId: string): Promise<void>;
+/** Adds an employee to several outlets at once. Scheduling does not require a POS role, so the
+ * caller may pass an empty role id and assign the POS role later from Employee. */
+export declare function addEmployeeToOutlets(employeeId: string, restaurantIds: string[], roleId?: string): Promise<void>;
 /** Takes a POS user off the given outlets' rosters; their other outlets are untouched. */
 export declare function removeEmployeeFromOutlets(employeeId: string, restaurantIds: string[]): Promise<void>;
 /** Takes a POS user off this outlet's roster only. */
 export declare function removeEmployeeFromOutlet(employeeId: string): Promise<void>;
-/** Every outlet each person works at (POS user id → outlet ids). The roster above is fetched
- * FILTERED to one outlet, and a filtered read describes a person by that outlet alone, so the
- * full list has to come from an unfiltered read. Paged until the total is covered. A failure
- * leaves the map empty rather than failing the board: locations are display-only here. */
-export declare const employeeOutletIds: import("vue").ShallowRef<Record<string, string[]>, Record<string, string[]>>;
-/** Everyone in the business (POS user summaries: name, passcode, outlet roles), kept once and
- * shared by the locations map, "select existing employee", passcode prefill and the role edits —
- * the plain `/pos-users` read they used before returns every user-outlet row in one slow call. */
-export declare const businessEmployees: import("vue").ShallowRef<IFdtoPosUserSummary[], IFdtoPosUserSummary[]>;
 /** The cached business roster, fetched on first use. `force` re-reads it (after a write, or to
  * refresh a list that is already on screen). Concurrent callers share one request. */
 export declare function ensureBusinessEmployees(force?: boolean): Promise<IFdtoPosUserSummary[]>;
@@ -101,11 +54,9 @@ export declare function reload(): Promise<void>;
 export declare function createEmployeeProfile(req: FdtoScheduleCreateEmployeeProfileReq): Promise<void>;
 /** Edits a profile already on this outlet's schedule. The caller (useScheduleAddEmployee's
  * `updateExisting`) applies the form to the live `Employee` object itself for instant feedback,
- * so this does not bump `dataVersion` — nothing needs a re-derive right now. It still patches
- * the entry inside `payload.value.employees` in place, though: that raw array is what the NEXT
- * re-derive (the next employee added, the next outlet reload) rebuilds every `Employee` from,
- * and a stale entry there would silently revert this edit the moment something else triggers
- * one, exactly the trap `createEmployeeProfile` above avoids by pushing onto the same array. */
+ * so this does not bump `dataVersion` — nothing needs a board cache rebuild. The raw payload is
+ * still replaced immutably so other views, such as the position usage counter, observe the
+ * profile change immediately instead of waiting for the next full board reload. */
 export declare function updateEmployeeProfile(employeeId: string, req: FdtoScheduleUpdateEmployeeProfileReq): Promise<void>;
 /** Positions are business-level, not per-outlet (see `ScheduleAPI.createPosition`'s own note)
  * — so unlike the shift-shaped writes below, there's no "discards an unsaved shift" risk in
@@ -134,7 +85,9 @@ export declare function saveDemand(req: ScheduleReplaceDemandReq): Promise<void>
  * week, so repeating it per date would only shadow later edits to the rule. Returns how many rows
  * were written. */
 export declare function copyDateDemand(fromDate: string, toDate: string): Promise<number>;
-export declare function generateAutoSchedule(req: FdtoScheduleAutoScheduleReq): Promise<FdtoScheduleAutoScheduleResult>;
+export declare function generateAutoSchedule(req: FdtoScheduleAutoScheduleGenerateReq): Promise<FdtoScheduleAutoScheduleResult>;
+export declare function getAutoScheduleCapabilities(): Promise<FdtoScheduleAutoScheduleCapabilities>;
+export declare function applyAutoSchedule(req: FdtoScheduleAutoScheduleApplyReq): Promise<FdtoScheduleAutoScheduleApplyResult>;
 /** A one-off shift assignment — someone working these hours on this date, not answering any
  * Shift requirement. Deliberately does not reload: unlike `createEmployeeProfile` above, there
  * is nothing here a reload could bring back that the caller doesn't already have — `commitShift`
@@ -146,6 +99,9 @@ export declare function updateAssignment(id: string, req: FdtoScheduleSaveAssign
 /** Deletes a batch of existing assignments in a single request — see
  * `ScheduleAPI.deleteAssignments`. Deleting one is just this with a single-id array. */
 export declare function deleteAssignments(ids: string[]): Promise<void>;
+export declare function createTimeOff(req: FdtoScheduleCreateTimeOffReq): Promise<FdtoScheduleTimeOff>;
+export declare function updateTimeOffStatus(id: string, req: FdtoScheduleUpdateTimeOffStatusReq): Promise<FdtoScheduleTimeOff | null>;
+export declare function deleteTimeOff(id: string): Promise<void>;
 /** Flips a batch of existing assignments to one status in a single request — see
  * `ScheduleAPI.bulkUpdateAssignmentStatus`. */
 export declare function bulkUpdateAssignmentStatus(req: FdtoScheduleBulkUpdateAssignmentStatusReq): Promise<FdtoScheduleAssignment[]>;

package/dist/src/views/scheduling/types.d.ts

@@ -18,11 +18,31 @@ export interface WorkSlot {
      * subtracted by the cost rail / stats row's hour totals — those stay gross-hours,
      * matching how this board priced shifts before the popover surfaced a break field. */
     breakMins?: number;
-    /** The ShiftAssignments document this slot is saved as, once it has one — see
+    /** Breaks as persisted by ScheduleShiftAssignments. `breakMins` remains a derived board calculation
+     * value; API writes use only this array. */
+    breaks?: Array<{
+        type: 'DURATION';
+        minutes: number;
+        breakPayType: 'PAID' | 'UNPAID';
+    } | {
+        type: 'TIME_RANGE';
+        startTime: string;
+        endTime: string;
+        breakPayType: 'PAID' | 'UNPAID';
+    }>;
+    /** The ScheduleShiftAssignments document this slot is saved as, once it has one — see
      * useScheduleBoard's commitShift/removeShift/moveShift. Absent means either it hasn't
      * round-tripped to the backend yet, or it's an OpenShift fill (see openId), which has its
      * own record shape and no write path of its own yet. */
     assignmentId?: string;
+    /** Client-only — never sent to the backend (there's no linking field in
+     * FdtoScheduleAssignment to persist it against). Shared by every period of ONE shift
+     * authored through the popover's "+ Split", set there and nowhere else. Two workslots on
+     * the same day with no matching `splitGroupId` are two independent shifts, not one split
+     * shift — e.g. a day where a swap landed a second shift alongside one the person already
+     * had. Lost on reload, which is the safe direction to fail in: an unrecognised pair just
+     * reads as two separate shifts rather than a false merge. */
+    splitGroupId?: string;
 }
 export interface LeaveBalance {
     type: string;
@@ -31,10 +51,13 @@ export interface LeaveBalance {
 }
 export interface LeaveSlot {
     timeOff: 'approved' | 'pending';
+    requestId?: string;
+    type?: 'OFF_DAY' | 'LEAVE';
+    leaveType?: 'ANNUAL' | 'MEDICAL' | 'EMERGENCY' | 'UNPAID';
     reason: string;
     half?: boolean;
     halfPart?: 'AM' | 'PM';
-    /** Specific hours (HH:MM), for leave that is neither all day nor a morning / afternoon. */
+    /** Half-day leave's displayed time window, when supplied by the board data. */
     from?: string;
     to?: string;
     appliedOn?: string;
@@ -63,6 +86,7 @@ export interface EmployeeAvailHours {
 export interface Employee {
     id: number;
     name: string;
+    employmentType: 'FULLTIME' | 'PARTTIME';
     role: string;
     initials: string;
     color: string;
@@ -313,6 +337,9 @@ export interface Proposal {
     start: string;
     end: string;
     role: string;
+    /** The position backing `role`, when the auto-schedule result named one. `null`/absent means
+     * any position (an unnamed need). */
+    positionId?: string | null;
     /** Set when this proposal would fill a named OpenShift record. */
     openId?: number;
     status: 'pending' | 'rejected';