@freedom_sky/feige-lib 5.21.0 → 5.23.0

package/.eslintignore

@@ -1,3 +1,3 @@
-dist
-node_modules
+dist
+node_modules
 jest.config.js

package/.eslintrc.js

@@ -1,16 +1,16 @@
-  module.exports = {
-    parser: "@typescript-eslint/parser", // Specifies the ESLint parser
-    extends: [
-      "plugin:@typescript-eslint/recommended", // Uses the recommended rules from the @typescript-eslint/eslint-plugin
-      "prettier/@typescript-eslint", // Uses eslint-config-prettier to disable ESLint rules from @typescript-eslint/eslint-plugin that would conflict with prettier
-      "plugin:jsdoc/recommended",
-      "plugin:prettier/recommended" // Enables eslint-plugin-prettier and eslint-config-prettier. This will display prettier errors as ESLint errors. Make sure this is always the last configuration in the extends array.
-    ],
-    parserOptions: {
-      ecmaVersion: 2018, // Allows for the parsing of modern ECMAScript features
-      sourceType: "module" // Allows for the use of imports
-    },
-    rules: {
-      '@typescript-eslint/no-use-before-define': 'off',
-    },
+  module.exports = {
+    parser: "@typescript-eslint/parser", // Specifies the ESLint parser
+    extends: [
+      "plugin:@typescript-eslint/recommended", // Uses the recommended rules from the @typescript-eslint/eslint-plugin
+      "prettier/@typescript-eslint", // Uses eslint-config-prettier to disable ESLint rules from @typescript-eslint/eslint-plugin that would conflict with prettier
+      "plugin:jsdoc/recommended",
+      "plugin:prettier/recommended" // Enables eslint-plugin-prettier and eslint-config-prettier. This will display prettier errors as ESLint errors. Make sure this is always the last configuration in the extends array.
+    ],
+    parserOptions: {
+      ecmaVersion: 2018, // Allows for the parsing of modern ECMAScript features
+      sourceType: "module" // Allows for the use of imports
+    },
+    rules: {
+      '@typescript-eslint/no-use-before-define': 'off',
+    },
   };

package/.prettierrc.js

@@ -1,7 +1,7 @@
-module.exports = {
-    semi: true,
-    trailingComma: "all",
-    singleQuote: true,
-    printWidth: 120,
-    tabWidth: 4
+module.exports = {
+    semi: true,
+    trailingComma: "all",
+    singleQuote: true,
+    printWidth: 120,
+    tabWidth: 4
   };

package/AGENTS.md

@@ -1,75 +1,75 @@
-# AGENTS.md — feige-lib
-
-Shared business library consumed by every repo in the order-multi workspace
-(server, app, admin-server, admin-fe, client, etc.). Anything here is, by
-definition, **shared** — changes ripple across the whole system.
-
-## Local-dev distribution
-
-This package is published to npm. During cross-repo development you can iterate
-without bumping the version by rebuilding (`npx tsc`) and copying `dist/` into
-each consumer's `node_modules/@freedom_sky/feige-lib/dist/`. Only bump the
-version (`package.json` + `CHANGE.md`) and `npm publish` when you're ready to
-release — and only with explicit user approval.
-
----
-
-## `CONST.UPPER_LIMIT` — naming and authoring rules
-
-`Const.UPPER_LIMIT` (see `src/const/const.ts`) holds every validation upper
-bound used by DTOs / schemas / UI in the workspace. The prefix on each key
-encodes **which domain owns the concept** — and any feature in any repo may
-reuse that constant when they're referencing the same concept.
-
-| Prefix | Meaning | Examples |
-|---|---|---|
-| `<DOMAIN>_` (e.g. `DISH_`, `MEMBER_`, `STORE_`, `TABLE_`, `TAKEOUT_`, `SPECIFICATION_`, `RESERVATION_`) | The constant belongs to that domain. Any feature that references the same concept reuses this key as-is. | `DISH_NAME_MAX_LENGTH`, `DISH_COUNT_MAX`, `MEMBER_NOTE_MAX_LENGTH`, `RESERVATION_NOTE_MAX_LENGTH` |
-| `COMMON_` | Generic limit with no single domain owner — applies across many features. | `COMMON_HEADCOUNT_MAX`, `COMMON_CONTACT_NAME_MAX_LENGTH`, `COMMON_CONTACT_PHONE_MAX_LENGTH` |
-
-**Decision flow for a new entry:**
-
-1. **Does an existing domain already own this concept?** Scan
-   `UPPER_LIMIT` for a `<DOMAIN>_` prefix that matches semantically. If yes,
-   reuse the existing key — even if your current feature is something else.
-   Example: reservation needs a max "dish count" → use `DISH_COUNT_MAX`, **not**
-   `RESERVATION_DISH_COUNT_MAX` and **not** `COMMON_DISH_COUNT_MAX`. The
-   concept is owned by the dish domain; reservation is just referencing dish.
-2. **No existing domain prefix, but the concept spans multiple unrelated
-   features?** Use `COMMON_`. Example: `COMMON_HEADCOUNT_MAX` —
-   dine-in / takeout / reservation can all hold a headcount; no single domain
-   owns it.
-3. **No existing prefix and only one feature will ever care?** Use that
-   feature's prefix. Example: `RESERVATION_NOTE_MAX_LENGTH` — the reservation
-   note is reservation-specific.
-
-**Forbidden combinations:**
-
-- `COMMON_<DOMAIN>_*` (e.g. `COMMON_DISH_*`) — self-contradicting; the
-  presence of `DISH_` already says "this lives in the dish domain". Drop
-  the `COMMON_`.
-- `<FEATURE>_<OTHER_DOMAIN>_*` (e.g. `RESERVATION_DISH_*`) — don't graft
-  your feature's prefix onto a concept that already has a domain. Reuse the
-  domain key directly.
-
-**Authoring rules:**
-
-1. **Look for an existing hardcoded value before inventing one.** A lot of
-   limits in this codebase started life as magic numbers in DTOs (`@Max(1000)`,
-   `@Length(1, 50)`, …). When extracting, **copy the existing value**, don't
-   pick a new one. That way a future "unify all usages" pass is a no-op for
-   behavior. Document where the value came from in the PR description /
-   commit, e.g.:
-
-   > `DISH_COUNT_MAX = 1000` — copied from
-   > `order-multi-server/src/orders/dto/create-order/create-order-base.dto.ts:83`
-   > `@Max(1000)`.
-
-2. **If no precedent exists, ask the user** for the value — do not guess.
-3. **Do not retro-edit old code** in the same change. Add the constant and
-   point new code at it. Sweeping the old hardcodes is a separate, dedicated
-   task to keep diffs reviewable.
-4. **Names use SCREAMING_SNAKE_CASE.** Suffix conventions:
-   - String fields → `..._MAX_LENGTH`
-   - Numeric counts/amounts → `..._MAX` (or no suffix when the name is already
-     unambiguous, matching the existing entries like `DISH_PRICE`,
-     `WAITER_NUM`).
+# AGENTS.md — feige-lib
+
+Shared business library consumed by every repo in the order-multi workspace
+(server, app, admin-server, admin-fe, client, etc.). Anything here is, by
+definition, **shared** — changes ripple across the whole system.
+
+## Local-dev distribution
+
+This package is published to npm. During cross-repo development you can iterate
+without bumping the version by rebuilding (`npx tsc`) and copying `dist/` into
+each consumer's `node_modules/@freedom_sky/feige-lib/dist/`. Only bump the
+version (`package.json` + `CHANGE.md`) and `npm publish` when you're ready to
+release — and only with explicit user approval.
+
+---
+
+## `CONST.UPPER_LIMIT` — naming and authoring rules
+
+`Const.UPPER_LIMIT` (see `src/const/const.ts`) holds every validation upper
+bound used by DTOs / schemas / UI in the workspace. The prefix on each key
+encodes **which domain owns the concept** — and any feature in any repo may
+reuse that constant when they're referencing the same concept.
+
+| Prefix | Meaning | Examples |
+|---|---|---|
+| `<DOMAIN>_` (e.g. `DISH_`, `MEMBER_`, `STORE_`, `TABLE_`, `TAKEOUT_`, `SPECIFICATION_`, `RESERVATION_`) | The constant belongs to that domain. Any feature that references the same concept reuses this key as-is. | `DISH_NAME_MAX_LENGTH`, `DISH_COUNT_MAX`, `MEMBER_NOTE_MAX_LENGTH`, `RESERVATION_NOTE_MAX_LENGTH` |
+| `COMMON_` | Generic limit with no single domain owner — applies across many features. | `COMMON_HEADCOUNT_MAX`, `COMMON_CONTACT_NAME_MAX_LENGTH`, `COMMON_CONTACT_PHONE_MAX_LENGTH` |
+
+**Decision flow for a new entry:**
+
+1. **Does an existing domain already own this concept?** Scan
+   `UPPER_LIMIT` for a `<DOMAIN>_` prefix that matches semantically. If yes,
+   reuse the existing key — even if your current feature is something else.
+   Example: reservation needs a max "dish count" → use `DISH_COUNT_MAX`, **not**
+   `RESERVATION_DISH_COUNT_MAX` and **not** `COMMON_DISH_COUNT_MAX`. The
+   concept is owned by the dish domain; reservation is just referencing dish.
+2. **No existing domain prefix, but the concept spans multiple unrelated
+   features?** Use `COMMON_`. Example: `COMMON_HEADCOUNT_MAX` —
+   dine-in / takeout / reservation can all hold a headcount; no single domain
+   owns it.
+3. **No existing prefix and only one feature will ever care?** Use that
+   feature's prefix. Example: `RESERVATION_NOTE_MAX_LENGTH` — the reservation
+   note is reservation-specific.
+
+**Forbidden combinations:**
+
+- `COMMON_<DOMAIN>_*` (e.g. `COMMON_DISH_*`) — self-contradicting; the
+  presence of `DISH_` already says "this lives in the dish domain". Drop
+  the `COMMON_`.
+- `<FEATURE>_<OTHER_DOMAIN>_*` (e.g. `RESERVATION_DISH_*`) — don't graft
+  your feature's prefix onto a concept that already has a domain. Reuse the
+  domain key directly.
+
+**Authoring rules:**
+
+1. **Look for an existing hardcoded value before inventing one.** A lot of
+   limits in this codebase started life as magic numbers in DTOs (`@Max(1000)`,
+   `@Length(1, 50)`, …). When extracting, **copy the existing value**, don't
+   pick a new one. That way a future "unify all usages" pass is a no-op for
+   behavior. Document where the value came from in the PR description /
+   commit, e.g.:
+
+   > `DISH_COUNT_MAX = 1000` — copied from
+   > `order-multi-server/src/orders/dto/create-order/create-order-base.dto.ts:83`
+   > `@Max(1000)`.
+
+2. **If no precedent exists, ask the user** for the value — do not guess.
+3. **Do not retro-edit old code** in the same change. Add the constant and
+   point new code at it. Sweeping the old hardcodes is a separate, dedicated
+   task to keep diffs reviewable.
+4. **Names use SCREAMING_SNAKE_CASE.** Suffix conventions:
+   - String fields → `..._MAX_LENGTH`
+   - Numeric counts/amounts → `..._MAX` (or no suffix when the name is already
+     unambiguous, matching the existing entries like `DISH_PRICE`,
+     `WAITER_NUM`).

package/CHANGE.md

@@ -1,32 +1,38 @@
-# 5.21.0
-- add ReservationStatusEnum (WAITING / CANCELLED / COMPLETED) for cross-repo reservation feature
-- add UPPER_LIMIT constants: COMMON_HEADCOUNT_MAX, COMMON_CONTACT_NAME_MAX_LENGTH, COMMON_CONTACT_PHONE_MAX_LENGTH, DISH_COUNT_MAX, DISH_NOTE_MAX_LENGTH, RESERVATION_NOTE_MAX_LENGTH
-- add AGENTS.md documenting UPPER_LIMIT naming rules (COMMON_ vs domain prefix)
-# 5.20.0
-- add ADDRESS_DETAIL_MAX_LENGTH constant
-# 5.19.0
-- add Store.location field for map-location feature
-# 4.45.0
-- add store auditedNames
-# 4.44.0
-- add half hour timezone
-# 4.43.0
-- add Czech language
-# 4.42.0
-- add STORE_DESCRIPTION_MAX_LENGTH
-# 4.41.0
-- add currency CZK
-# 4.40.0
-- add proclamationPopUp
-
-# 4.39.0
-- add China Kazakh language kk-Arab-CN
-
-# 4.38.1
-- change ug dateFormat to DateFormat.YEAR_MONTH_DAY,
-
-# 4.38.0
-- add extendedPrintingLangs and multiLangDirection to store printer interface
-
-# 4.37.0
-- add MultiLangDirectionEnum
+# 5.23.0
+- add shared ascending and descending sort direction enum
+- add MAD and AOA currency formatting and Angola regional defaults
+- make balance settlement currency-aware for large currencies
+# 5.22.0
+- add Reservation and ReservationDish interfaces for cross-repo reservation feature (ReservationDish.type uses DishType enum; Reservation.status uses ReservationStatusEnum; Reservation.addTime accepts Date | string for BSON/wire compatibility)
+# 5.21.0
+- add ReservationStatusEnum (WAITING / CANCELLED / COMPLETED) for cross-repo reservation feature
+- add UPPER_LIMIT constants: COMMON_HEADCOUNT_MAX, COMMON_CONTACT_NAME_MAX_LENGTH, COMMON_CONTACT_PHONE_MAX_LENGTH, DISH_COUNT_MAX, DISH_NOTE_MAX_LENGTH, RESERVATION_NOTE_MAX_LENGTH
+- add AGENTS.md documenting UPPER_LIMIT naming rules (COMMON_ vs domain prefix)
+# 5.20.0
+- add ADDRESS_DETAIL_MAX_LENGTH constant
+# 5.19.0
+- add Store.location field for map-location feature
+# 4.45.0
+- add store auditedNames
+# 4.44.0
+- add half hour timezone
+# 4.43.0
+- add Czech language
+# 4.42.0
+- add STORE_DESCRIPTION_MAX_LENGTH
+# 4.41.0
+- add currency CZK
+# 4.40.0
+- add proclamationPopUp
+
+# 4.39.0
+- add China Kazakh language kk-Arab-CN
+
+# 4.38.1
+- change ug dateFormat to DateFormat.YEAR_MONTH_DAY,
+
+# 4.38.0
+- add extendedPrintingLangs and multiLangDirection to store printer interface
+
+# 4.37.0
+- add MultiLangDirectionEnum

package/azure-pipelines-release.yml

@@ -0,0 +1,56 @@
+trigger:
+  branches:
+    exclude:
+      - '*'
+  tags:
+    include:
+      - 'release/v*'
+
+pr: none
+
+pool:
+  vmImage: ubuntu-latest
+
+steps:
+  - task: NodeTool@0
+    displayName: Use Node.js 18
+    inputs:
+      versionSpec: 18.x
+
+  - script: npm ci
+    displayName: Install dependencies
+
+  - script: npm run build
+    displayName: Test and build
+
+  - bash: |
+      set -euo pipefail
+
+      PACKAGE_NAME="$(node -p "require('./package.json').name")"
+      PACKAGE_VERSION="$(node -p "require('./package.json').version")"
+      EXPECTED_TAG="refs/tags/release/v$PACKAGE_VERSION"
+
+      if [ "$BUILD_SOURCEBRANCH" != "$EXPECTED_TAG" ]; then
+        echo "Expected tag $EXPECTED_TAG, got $BUILD_SOURCEBRANCH."
+        exit 1
+      fi
+
+      if [ -z "${NPM_TOKEN:-}" ] || [ "$NPM_TOKEN" = "SET_AT_RUN_TIME" ]; then
+        echo "NPM_TOKEN must be configured as a secret pipeline variable."
+        exit 1
+      fi
+
+      if npm view "$PACKAGE_NAME@$PACKAGE_VERSION" version --registry=https://registry.npmjs.org/ >/dev/null 2>&1; then
+        echo "$PACKAGE_NAME@$PACKAGE_VERSION is already published."
+        exit 1
+      fi
+
+      NPMRC="$AGENT_TEMPDIRECTORY/feige-lib.npmrc"
+      trap 'rm -f "$NPMRC"' EXIT
+      printf '//registry.npmjs.org/:_authToken=%s\n' "$NPM_TOKEN" > "$NPMRC"
+
+      npm whoami --userconfig "$NPMRC" --registry=https://registry.npmjs.org/
+      npm publish --ignore-scripts --userconfig "$NPMRC" --registry=https://registry.npmjs.org/ --access public
+    displayName: Publish npm package
+    env:
+      NPM_TOKEN: $(NPM_TOKEN)

package/dist/announcement/enum/announcement.enum.d.ts

@@ -1,11 +1,11 @@
-export declare enum AnnouncementTypeEnum {
-    Text = "text",
-    Image = "image"
-}
-export declare enum AnnouncementTargetEnum {
-    Table = "table",
-    Buffet = "buffet",
-    Serial = "serial",
-    PickUp = "pickup",
-    Delivery = "delivery"
-}
+export declare enum AnnouncementTypeEnum {
+    Text = "text",
+    Image = "image"
+}
+export declare enum AnnouncementTargetEnum {
+    Table = "table",
+    Buffet = "buffet",
+    Serial = "serial",
+    PickUp = "pickup",
+    Delivery = "delivery"
+}

package/dist/announcement/enum/announcement.enum.js

@@ -1,15 +1,15 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-var AnnouncementTypeEnum;
-(function (AnnouncementTypeEnum) {
-    AnnouncementTypeEnum["Text"] = "text";
-    AnnouncementTypeEnum["Image"] = "image";
-})(AnnouncementTypeEnum = exports.AnnouncementTypeEnum || (exports.AnnouncementTypeEnum = {}));
-var AnnouncementTargetEnum;
-(function (AnnouncementTargetEnum) {
-    AnnouncementTargetEnum["Table"] = "table";
-    AnnouncementTargetEnum["Buffet"] = "buffet";
-    AnnouncementTargetEnum["Serial"] = "serial";
-    AnnouncementTargetEnum["PickUp"] = "pickup";
-    AnnouncementTargetEnum["Delivery"] = "delivery";
-})(AnnouncementTargetEnum = exports.AnnouncementTargetEnum || (exports.AnnouncementTargetEnum = {}));
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+var AnnouncementTypeEnum;
+(function (AnnouncementTypeEnum) {
+    AnnouncementTypeEnum["Text"] = "text";
+    AnnouncementTypeEnum["Image"] = "image";
+})(AnnouncementTypeEnum = exports.AnnouncementTypeEnum || (exports.AnnouncementTypeEnum = {}));
+var AnnouncementTargetEnum;
+(function (AnnouncementTargetEnum) {
+    AnnouncementTargetEnum["Table"] = "table";
+    AnnouncementTargetEnum["Buffet"] = "buffet";
+    AnnouncementTargetEnum["Serial"] = "serial";
+    AnnouncementTargetEnum["PickUp"] = "pickup";
+    AnnouncementTargetEnum["Delivery"] = "delivery";
+})(AnnouncementTargetEnum = exports.AnnouncementTargetEnum || (exports.AnnouncementTargetEnum = {}));

package/dist/buffet/index.d.ts

@@ -1,46 +1,46 @@
-import { BuffetCombosItems, BuffetDishItem, Order } from '../index';
-/**
- * 计算自助餐总价
- */
-/**
- *
- */
-export declare function getDishItemInBuffet({ dishId, buffet, }: {
-    dishId: string;
-    buffet?: BuffetCombosItems;
-}): BuffetDishItem | undefined;
-/**
- *
- */
-export declare function getMaxBuffetDishUpperLimit({ buffetDishItem, adultNum, childNum, }: {
-    buffetDishItem: BuffetDishItem;
-    adultNum: number;
-    childNum: number;
-}): number;
-/**
- * @param buffetCombosItem
- * @param adultNum
- * @param childNum
- */
-export declare function calcBuffetTotalPrice(buffetCombosItem: BuffetCombosItems, adultNum: number, childNum: number): number;
-/**
- *
- */
-export declare function dishShowPriceWithBuffet({ dishPrice, dishId, buffet, orderedCound, adultNum, childNum, }: {
-    dishPrice: number;
-    dishId: string;
-    buffet?: BuffetCombosItems;
-    orderedCound: number;
-    adultNum: number;
-    childNum: number;
-}): number;
-/**
- *
- */
-export declare function getRoundCoundAndSecondsToNextTurn({ order, }: {
-    order: Order;
-}): {
-    roundCount?: number;
-    maxRounds?: number;
-    secondsToNextTurn: number;
-};
+import { BuffetCombosItems, BuffetDishItem, Order } from '../index';
+/**
+ * 计算自助餐总价
+ */
+/**
+ *
+ */
+export declare function getDishItemInBuffet({ dishId, buffet, }: {
+    dishId: string;
+    buffet?: BuffetCombosItems;
+}): BuffetDishItem | undefined;
+/**
+ *
+ */
+export declare function getMaxBuffetDishUpperLimit({ buffetDishItem, adultNum, childNum, }: {
+    buffetDishItem: BuffetDishItem;
+    adultNum: number;
+    childNum: number;
+}): number;
+/**
+ * @param buffetCombosItem
+ * @param adultNum
+ * @param childNum
+ */
+export declare function calcBuffetTotalPrice(buffetCombosItem: BuffetCombosItems, adultNum: number, childNum: number): number;
+/**
+ *
+ */
+export declare function dishShowPriceWithBuffet({ dishPrice, dishId, buffet, orderedCound, adultNum, childNum, }: {
+    dishPrice: number;
+    dishId: string;
+    buffet?: BuffetCombosItems;
+    orderedCound: number;
+    adultNum: number;
+    childNum: number;
+}): number;
+/**
+ *
+ */
+export declare function getRoundCoundAndSecondsToNextTurn({ order, }: {
+    order: Order;
+}): {
+    roundCount?: number;
+    maxRounds?: number;
+    secondsToNextTurn: number;
+};