@7365admin1/layer-common 3.2.2-staging.121 → 3.2.2-staging.123

package/.changeset/pm-sidebar-grouping-and-list-scaffold.md

@@ -1,27 +0,0 @@
----
-"@7365admin1/layer-common": patch
----
-
-Group the sidebar's sections and give the list screens the design's page
-scaffold.
-
-- `withSections()` walked each application's menu in the order it was given and
-  printed a heading whenever the section changed, so Property Management drew
-  SERVICE DESK, PROPERTY and SECURITY OPERATIONS **twice each**. Items are now
-  grouped under one heading per section, in the order the design lists them,
-  with the application's own order kept inside each section. No menu item is
-  added, hidden, renamed, re-routed or re-gated.
-- `ServiceProviderMain`, `FeedbackMain`, `InvitationMain` and `WorkOrder/Main`
-  had no page title, put their primary action top-left, floated the search
-  outside the card, and stacked the refresh/pager on a bar above the tabs. They
-  now use `PageHeader` / `AppCard` / `CardToolbar` / `AppButton` / `AppField`:
-  a 22px title with the action on the right, then one in-card row with the tabs
-  on the left and search, count and pager on the right.
-- `SwitchContext` and the rail's application name print in full instead of
-  truncating to "Seventh Cond…" / "Property Managem…".
-- The security dashboard's `ACTIVE PATROL` / `STAFF STATUS` panel headings are
-  written the way the design writes them, matching their sibling panels.
-
-Placement and wording only: the same buttons open the same dialogs under the
-same permissions, the same tabs load the same lists, and the tables, columns,
-filters and row menus are untouched.

package/.changeset/service-provider-invitation-actions.md

@@ -1,28 +0,0 @@
----
-"@7365admin1/layer-common": minor
----
-
-Make the Pending tab's invitation actions reachable, and say which state an invitation is really in
-
-The row menu in the service-provider list was drawn only for provider rows, so a
-pending invitation offered no actions at all — including the cancel that was
-already wired up behind it. Invitation rows now carry Cancel, Resend and Delete,
-each behind a confirmation that names the company and the site, and Resend is
-disabled with the reason while Seven365 has not approved the invitation yet.
-
-Every invitation also used to read "Pending" whatever had happened to it. Rows
-now show the state they are actually in — Waiting for Seven365, Waiting for the
-provider, Not approved, Declined, Cancelled, Expired — in those words, with
-Seven365's reason shown underneath a rejected one.
-
-Also here: a new ServiceProviderInvitationPrompt, which is how an existing
-provider answers an invitation from inside the app they already use, with no
-sign-up and no one-time code.
-
-Three contrast fixes found while rendering these screens: the list's tab strip
-was a hardcoded light grey that turned into a white slab in dark mode and took
-the tab labels with it; the service type column read the raw stored slug
-("security_agency") instead of "Security"; and `on-warning`, `on-info` and
-dark's `on-error` are now set explicitly, because Vuetify derives white for them
-and that measures 2.37:1, 3.12:1 and 3.60:1 on those fills — every filled
-warning, info and error chip, alert and button in the product.

package/.editorconfig

@@ -1,12 +0,0 @@
-root = true
-
-[*]
-indent_size = 2
-indent_style = space
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-
-[*.md]
-trim_trailing_whitespace = false

package/.github/workflows/main.yml

@@ -1,17 +0,0 @@
-name: CI
-on:
-  push:
-    branches:
-      - "**"
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20.x
-          cache: "yarn"
-      - run: yarn install --frozen-lockfile && yarn dev:prepare
-      - run: yarn build

package/.github/workflows/publish-staging.yml

@@ -1,47 +0,0 @@
-name: Publish Staging
-on:
-  push:
-    branches:
-      - staging
-
-concurrency: ${{ github.workflow }}-${{ github.ref }}
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20.x
-          cache: "yarn"
-          cache-dependency-path: yarn.lock
-
-      - run: yarn install --immutable
-
-      - run: yarn build
-
-      - name: Create .npmrc for publishing
-        run: |
-          echo '//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}' > ~/.npmrc
-
-      - name: Set staging prerelease version
-        run: |
-          BASE=$(node -p "const [x,y,z]=require('./package.json').version.split('-')[0].split('.'); [x,y,+z+1].join('.')")
-          npm version "$BASE-staging.${{ github.run_number }}" --no-git-tag-version
-          node -p "'Publishing ' + require('./package.json').version"
-
-      - name: Publish to npm with staging tag
-        run: npm publish --tag staging --registry https://registry.npmjs.org
-
-      - name: Notify Discord on failure
-        if: failure()
-        env:
-          DISCORD_WEBHOOK_URL: ${{ secrets.DISCORD_WEBHOOK_URL }}
-        run: |
-          MESSAGE="@everyone :rotating_light: **Publish Staging** failed in \`${{ github.repository }}\` (\`${{ github.workflow }}\`)
-          ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
-          curl -s -X POST -H "Content-Type: application/json" \
-            -d "$(jq -n --arg content "$MESSAGE" '{content: $content}')" \
-            "$DISCORD_WEBHOOK_URL"

package/.github/workflows/publish.yml

@@ -1,39 +0,0 @@
-name: Publish
-on:
-  workflow_run:
-    workflows: [CI]
-    branches: [main]
-    types: [completed]
-
-concurrency: ${{ github.workflow }}-${{ github.ref }}
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  publish:
-    if: ${{ github.event.workflow_run.conclusion == 'success' }}
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20.x
-          cache: "yarn" # Use yarn for caching
-          cache-dependency-path: yarn.lock # Cache Yarn lockfile
-
-      - run: yarn install --immutable # Install dependencies with immutable lockfile
-
-      - name: Create .npmrc for publishing
-        run: |
-          echo '//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}' > ~/.npmrc
-
-      - name: Create Release Pull Request or Publish
-        id: changesets
-        uses: changesets/action@v1
-        with:
-          publish: yarn release # Use yarn for publishing
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

package/PUBLISHING.md

@@ -1,269 +0,0 @@
-# Publishing Guide
-
-This document explains how to publish new versions of `@7365admin1/layer-common` to npm using changesets and GitHub Actions.
-
-## Overview
-
-The package uses an automated publishing workflow powered by [Changesets](https://github.com/changesets/changesets) and GitHub Actions. When you make changes and create a changeset, the workflow automatically:
-
-1. Creates a "Version Packages" PR with version bumps
-2. Publishes to npm when you merge that PR
-
-## Quick Start
-
-### 1. Make Your Changes
-
-Make your code changes in a new branch as usual.
-
-### 2. Create a Changeset
-
-Before committing, create a changeset to document your changes:
-
-```bash
-npx changeset
-```
-
-You'll be prompted to:
-- Select the type of change: `patch`, `minor`, or `major`
-- Write a summary of your changes
-
-This creates a `.changeset/[random-name].md` file.
-
-### 3. Commit and Push
-
-```bash
-git add .
-git commit -m "feat: your feature description"
-git push
-```
-
-### 4. Create a Pull Request
-
-Create a PR to merge your branch into `main`.
-
-### 5. Merge Your PR
-
-Once approved, merge your PR to `main`.
-
-### 6. Bot Creates Version PR (Automatic)
-
-After merging, the GitHub Actions bot will automatically:
-- Detect your changeset
-- Create a new PR titled "Version Packages"
-- Update `package.json` with the new version
-- Update `CHANGELOG.md`
-- Remove the changeset file
-
-### 7. Merge the Version PR
-
-Review and merge the "Version Packages" PR. This will:
-- Bump the version in `package.json`
-- Automatically publish to npm 🚀
-
-## Workflow Diagram
-
-```
-You: Make changes + create changeset
-         ↓
-You: Push and create PR
-         ↓
-You: Merge PR to main
-         ↓
-Bot: Creates "Version Packages" PR (automatic)
-         ↓
-You: Merge "Version Packages" PR
-         ↓
-Bot: Publishes to npm (automatic)
-```
-
-## Version Types
-
-When creating a changeset, you'll choose a version bump type:
-
-- **patch** (1.8.0 → 1.8.1): Bug fixes, minor changes
-- **minor** (1.8.0 → 1.9.0): New features, backward compatible
-- **major** (1.8.0 → 2.0.0): Breaking changes
-
-## Common Commands
-
-### Create a Changeset
-```bash
-npx changeset
-```
-
-### Create an Empty Changeset
-```bash
-npx changeset add --empty
-```
-
-### Check Which Packages Would Be Published
-```bash
-npx changeset status
-```
-
-### Manually Version (Local Testing Only)
-```bash
-npx changeset version
-```
-
-### Manually Publish (Not Recommended)
-```bash
-yarn run release
-```
-> ⚠️ **Note**: Manual publishing requires 2FA or an automation token. Use GitHub Actions instead.
-
-## GitHub Setup
-
-### Required Secrets
-
-The repository needs the following GitHub secret:
-
-**`NPM_TOKEN`**
-- Location: Settings → Secrets and variables → Actions
-- Type: Granular Access Token (Automation)
-- Value: Your npm automation token
-- Permissions: Read and Write for packages, with 2FA bypass enabled
-
-### Workflow Files
-
-- `.github/workflows/main.yml` - CI workflow (builds and tests)
-- `.github/workflows/publish.yml` - Publish workflow (creates PRs and publishes)
-
-## Configuration Files
-
-### `.changeset/config.json`
-
-```json
-{
-  "$schema": "https://unpkg.com/@changesets/config@3.0.5/schema.json",
-  "changelog": "@changesets/cli/changelog",
-  "commit": false,
-  "access": "public",
-  "baseBranch": "main"
-}
-```
-
-Key settings:
-- `"access": "public"` - Package is published as public (free)
-- `"baseBranch": "main"` - PRs are created against main
-
-### `package.json`
-
-```json
-{
-  "name": "@7365admin1/layer-common",
-  "version": "1.8.1",
-  "author": "7365admin1",
-  "publishConfig": {
-    "access": "public"
-  }
-}
-```
-
-Key settings:
-- `"publishConfig.access": "public"` - Ensures scoped package is public
-
-## Troubleshooting
-
-### "Version didn't update on npm"
-
-**Solution**: Make sure you merged the bot's "Version Packages" PR. The version only publishes after merging that PR, not your original PR.
-
-### "No Version Packages PR was created"
-
-**Possible causes**:
-1. No changeset file was committed
-2. CI workflow failed
-3. Check GitHub Actions logs for errors
-
-**Solution**: Run `npx changeset status` locally to verify changesets exist.
-
-### "402 Payment Required" Error
-
-**Cause**: Scoped packages (`@username/package`) are private by default and require payment.
-
-**Solution**: Ensure `publishConfig.access` is set to `"public"` in `package.json`.
-
-### "403 Forbidden" or "401 Unauthorized"
-
-**Cause**: Invalid or expired npm token.
-
-**Solution**: 
-1. Generate a new Granular Access Token (Automation type) on npmjs.com
-2. Update the `NPM_TOKEN` secret in GitHub
-3. Ensure token has "Bypass 2FA" enabled
-
-### "Changeset not found" Error
-
-**Cause**: Changeset file wasn't committed or was deleted.
-
-**Solution**: Run `npx changeset` again and commit the generated `.changeset/*.md` file.
-
-## Best Practices
-
-### 1. Always Create Changesets
-
-Never merge code changes without a changeset. It ensures:
-- Version tracking
-- Changelog updates
-- Proper npm publishing
-
-### 2. Write Clear Changeset Summaries
-
-Your changeset summary becomes the changelog entry. Make it:
-- Clear and concise
-- User-focused (what changed, not how)
-- Action-oriented (e.g., "Added X feature" not "Adding X feature")
-
-### 3. Don't Skip the Version PR
-
-Always review and merge the "Version Packages" PR. It shows exactly what will be published.
-
-### 4. Use Yarn for Local Development
-
-The project uses Yarn for dependency management:
-
-```bash
-yarn install
-yarn dev
-yarn build
-```
-
-### 5. Keep `.npmrc` Private
-
-The `.npmrc` file contains your authentication token. It's in `.gitignore` - **never commit it!**
-
-## Security
-
-### npm Authentication
-
-- **GitHub Actions**: Uses `NPM_TOKEN` secret (automation token)
-- **Local Publishing**: Uses `.npmrc` file (not committed to git)
-
-### Token Types
-
-- **Automation tokens**: Bypass 2FA, designed for CI/CD
-- **Publish tokens**: Require 2FA, for manual publishing
-
-Always use automation tokens for GitHub Actions.
-
-## Package Information
-
-- **Name**: `@7365admin1/layer-common`
-- **Registry**: https://registry.npmjs.org/
-- **Package Page**: https://www.npmjs.com/package/@7365admin1/layer-common
-- **Author**: 7365admin1
-- **License**: MIT
-
-## Need Help?
-
-If you encounter issues:
-
-1. Check the [Changesets documentation](https://github.com/changesets/changesets)
-2. Review GitHub Actions workflow logs
-3. Verify npm token is valid and has correct permissions
-4. Ensure `.changeset/config.json` has `"access": "public"`
-
----
-
-**Last Updated**: January 2026

package/components/ScheduleTaskAreaFormDialog.vue

@@ -1,141 +0,0 @@
-<template>
-  <v-dialog
-    :model-value="modelValue"
-    @update:model-value="(v) => emit('update:modelValue', v)"
-    max-width="520"
-  >
-    <!-- 520px is the handoff's `--modal-w`, and the card wears `.screen-modal`
-         for the 16px corner, the `--card` surface and the modal shadow. The
-         two `v-toolbar`s standing in for the title row and the footer were
-         fixed grey slabs that stay grey on the dark theme, and the Create
-         button was a hardcoded `color="black"` fill on a `rounded-0` square. -->
-    <v-card class="screen-modal">
-      <template v-if="$slots.header">
-        <slot
-          name="header"
-          :title="
-            mode === 'edit' ? `Edit ${entityType}` : `Add New ${entityType}`
-          "
-          :onClose="onClose"
-        />
-      </template>
-      <v-card-title v-else class="text-capitalize">{{
-        mode === "edit" ? `Edit ${entityType}` : `Add New ${entityType}`
-      }}</v-card-title>
-
-      <v-card-text class="screen-modal__body">
-        <v-form ref="formRef" v-model="valid">
-          <v-row>
-            <v-col cols="12">
-              <InputLabel for="name" :title="label" required />
-              <!-- Still a `v-text-field`: Submit is gated on `valid`, which
-                   only exists because this `:rules` runs. `.filter-field` gives
-                   it the design's 40px / 10px / 13.5px shape without taking the
-                   validation away. -->
-              <v-text-field
-                v-model="nameValue"
-                class="filter-field"
-                :rules="[requiredRule]"
-              />
-            </v-col>
-          </v-row>
-        </v-form>
-      </v-card-text>
-
-      <div class="screen-modal__footer">
-        <v-btn
-          variant="outlined"
-          class="screen-btn-ghost"
-          @click="close"
-        >
-          Cancel
-        </v-btn>
-
-        <!-- Kept a `v-btn`: `loading` is the only in-flight signal this form
-             has, and `AppButton` has no equivalent. -->
-        <v-btn
-          variant="flat"
-          class="screen-btn-primary"
-          :loading="submitting"
-          @click="submit"
-        >
-          {{ mode === "edit" ? "Save" : "Create" }}
-        </v-btn>
-      </div>
-    </v-card>
-  </v-dialog>
-</template>
-
-<script setup lang="ts">
-const props = defineProps({
-  modelValue: { type: Boolean, required: true },
-  mode: { type: String as PropType<"add" | "edit">, default: "add" },
-  area: { type: Object as PropType<Record<string, any> | null>, default: null },
-  label: { type: String, default: "Name" },
-  nameModel: { type: String as PropType<string | null>, default: null },
-  entityType: { type: String, default: "Area" }, // values: "Area", "Unit"
-});
-
-const emit = defineEmits([
-  "update:modelValue",
-  "saved",
-  "update:nameModel",
-] as const);
-
-const formRef = ref(null);
-const valid = ref(false);
-const submitting = ref(false);
-
-const form = reactive({ name: "", description: "", status: "active" });
-
-watchEffect(() => {
-  if (props.area) {
-    form.name = props.area.name || "";
-    form.description = props.area.description || "";
-    form.status = props.area.status || "active";
-  } else {
-    form.name = "";
-    form.description = "";
-    form.status = "active";
-  }
-});
-
-const { requiredRule } = useUtils();
-
-const nameValue = computed({
-  get: () => {
-    return props.nameModel !== null ? props.nameModel : form.name;
-  },
-  set: (v: string) => {
-    if (props.nameModel !== null) {
-      emit("update:nameModel", v);
-    } else {
-      form.name = v;
-    }
-  },
-});
-
-function close() {
-  emit("update:modelValue", false);
-}
-
-const onClose = () => close();
-
-async function submit() {
-  if (!valid.value) return;
-  submitting.value = true;
-  try {
-    await new Promise((r) => setTimeout(r, 500));
-    emit("saved", { ...form, _id: props.area?._id || Date.now().toString() });
-
-    form.name = "";
-    form.description = "";
-    form.status = "active";
-
-    emit("update:modelValue", false);
-  } catch (e) {
-  } finally {
-    submitting.value = false;
-  }
-}
-</script>

package/components/ScheduleTaskAreaUpdateMoreAction.vue

@@ -1,104 +0,0 @@
-<template>
-  <!-- The schedule-area copy of `Dialog/UpdateMoreAction`, converted the same
-       way: two `v-toolbar`s (fixed grey slabs that stay grey on the dark
-       theme) for the title row and the footer, and a hardcoded `color="black"`
-       fill on a square 48px tile. -->
-  <v-card class="screen-modal" width="100%">
-    <template v-if="$slots.header">
-      <slot name="header" :title="title" :onClose="onClose" />
-    </template>
-    <v-card-title v-else class="text-capitalize">{{ title }}</v-card-title>
-
-    <v-card-text class="screen-modal__body pb-0">
-      <slot name="content" />
-    </v-card-text>
-
-    <div class="screen-modal__footer">
-      <v-btn
-        variant="outlined"
-        class="screen-btn-ghost"
-        @click="emit('close')"
-      >
-        Close
-      </v-btn>
-
-      <v-menu>
-        <template #activator="{ props }">
-          <v-btn
-            variant="flat"
-            class="screen-btn-primary"
-            v-bind="props"
-          >
-            More actions
-          </v-btn>
-        </template>
-
-        <!-- Dropdown shape left as Vuetify draws it - the handoff specifies
-             the profile dropdown only. `text-red` (Vuetify's fixed #f44336,
-             the same red on both themes) becomes `text-error`, which is
-             `--v-theme-error`, i.e. the design's `--err`, matching the
-             handoff's "red Logout row (err color, err-bg hover)". -->
-        <v-list class="pa-0 area-more__list">
-          <v-list-item v-if="canUpdate" @click="emit('edit')">
-            <v-list-item-title>
-              {{ editButtonLabel }}
-            </v-list-item-title>
-          </v-list-item>
-
-          <v-list-item
-            v-if="canDelete"
-            @click="emit('delete')"
-            class="text-error"
-          >
-            <v-list-item-title>
-              {{ deleteButtonLabel }}
-            </v-list-item-title>
-          </v-list-item>
-        </v-list>
-      </v-menu>
-    </div>
-  </v-card>
-</template>
-
-<script setup lang="ts">
-const prop = defineProps({
-  canUpdate: {
-    type: Boolean,
-    default: true,
-  },
-  canDelete: {
-    type: Boolean,
-    default: true,
-  },
-  editButtonLabel: {
-    type: String,
-    default: "Edit Area",
-  },
-  deleteButtonLabel: {
-    type: String,
-    default: "Delete Area",
-  },
-  title: {
-    type: String,
-    default: "Area Actions",
-  },
-});
-
-const emit = defineEmits(["close", "manage", "edit", "delete"]);
-const {
-  canUpdate,
-  editButtonLabel,
-  deleteButtonLabel,
-  manageButtonLabel,
-  title,
-} = prop;
-</script>
-
-<style scoped>
-/* `text-subtitle-2` was Vuetify's 0.875rem/500; the handoff names no type for
-   a menu row, so it takes the established cell type. */
-.area-more__list :deep(.v-list-item-title) {
-  font-size: var(--fs-cell);
-  font-weight: var(--fw-cell);
-}
-</style>