@thejob/schema 2.1.3 → 2.1.5

package/.claude/settings.local.json

@@ -112,11 +112,11 @@
       "Bash(grep -n 'data\\\\.dict\\\\|dict\\\\b\\\\|$props\\\\|export let' /home/nadeem/Documents/GitHub/thejob-svelte-ui/src/lib/onboarding/wizards/job-seeker-wizard.svelte)",
       "Bash(grep -v \"^$\")",
       "Bash(grep -E '^\\\\s+\"[a-zA-Z]+\":\\\\s*\\\\{$' src/lib/i18n/dictionaries/en.json)",
-      "Bash(sed -i 's|<title>Job search timeline - TheJob</title>|<title>{\\(data.dict?.pageTitles?.preferencesUrgency ?? \"Job search timeline\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"TheJob\"\\)}</title>|' urgency/+page.svelte)",
-      "Bash(sed -i 's|<title>Job locations - TheJob</title>|<title>{\\(data.dict?.pageTitles?.preferencesLocations ?? \"Job locations\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"TheJob\"\\)}</title>|' locations/+page.svelte)",
-      "Bash(sed -i 's|<title>Minimum salary - TheJob</title>|<title>{\\(data.dict?.pageTitles?.preferencesSalary ?? \"Minimum salary\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"TheJob\"\\)}</title>|' salary/+page.svelte)",
-      "Bash(sed -i 's|<title>Job role - TheJob</title>|<title>{\\(data.dict?.pageTitles?.preferencesRole ?? \"Job role\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"TheJob\"\\)}</title>|' role/+page.svelte)",
-      "Bash(sed -i 's|<title>Experience level - TheJob</title>|<title>{\\(data.dict?.pageTitles?.preferencesExperience ?? \"Experience level\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"TheJob\"\\)}</title>|' experience/+page.svelte)",
+      "Bash(sed -i 's|<title>Job search timeline - The Job</title>|<title>{\\(data.dict?.pageTitles?.preferencesUrgency ?? \"Job search timeline\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"The Job\"\\)}</title>|' urgency/+page.svelte)",
+      "Bash(sed -i 's|<title>Job locations - The Job</title>|<title>{\\(data.dict?.pageTitles?.preferencesLocations ?? \"Job locations\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"The Job\"\\)}</title>|' locations/+page.svelte)",
+      "Bash(sed -i 's|<title>Minimum salary - The Job</title>|<title>{\\(data.dict?.pageTitles?.preferencesSalary ?? \"Minimum salary\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"The Job\"\\)}</title>|' salary/+page.svelte)",
+      "Bash(sed -i 's|<title>Job role - The Job</title>|<title>{\\(data.dict?.pageTitles?.preferencesRole ?? \"Job role\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"The Job\"\\)}</title>|' role/+page.svelte)",
+      "Bash(sed -i 's|<title>Experience level - The Job</title>|<title>{\\(data.dict?.pageTitles?.preferencesExperience ?? \"Experience level\"\\)} - {\\(data.dict?.pageTitles?.siteName ?? \"The Job\"\\)}</title>|' experience/+page.svelte)",
       "Bash(python3 -c \"import json; d=json.load\\(open\\('src/lib/i18n/dictionaries/en.json'\\)\\); import sys; json.dump\\(d.get\\('search',{}\\), sys.stdout, indent=2\\)\")",
       "Bash(python3 -c \"import json; d=json.load\\(open\\('src/lib/i18n/dictionaries/sv.json'\\)\\); import sys; sv=d.get\\('search',{}\\); print\\('HAS' if 'noResults' in sv else 'MISSING', 'sv search.noResults'\\)\")",
       "Bash(grep -n \"[^=>]\\\\\"[A-Z][a-z][^\\\\\"]\\\\{5,\\\\}\\\\\"\\\\|>[A-Z][a-z][^<]\\\\{5,\\\\}<\" src/routes/\\\\[country\\\\]/\\\\[lang\\\\]/profile/+page.svelte)",

package/CLAUDE.md

@@ -0,0 +1,85 @@
+# @thejob/schema — working notes for agents
+
+Read this before changing anything. Fourteen repos depend on this package; a
+careless edit here breaks all of them at once.
+
+## What this is
+
+The **single source of truth** for The Job's data shapes: Yup schemas plus the
+constants and enums that go with them. Plain Yup, no runtime dependencies, built
+with `tsup` to dual ESM/CJS.
+
+Current line is **v2** (branch `v2`, published `2.1.x`). v2 dropped v1's `objectId`
+and `oneOfSchema` extensions and uses import-type for types; only
+`date-string.extension.ts` remains.
+
+## Every schema lives here, and only here
+
+**Never hand-roll a `yup.object` in a consuming service.** If a service needs a
+partial validator, it derives one inline:
+
+```ts
+UserSchema.pick(['headline', 'aboutMe'])
+GroupSchema.omit(['createdAt', 'updatedAt'])
+```
+
+Do **not** add `Update*Schema` / `Create*Schema` wrapper exports here for that
+purpose — the pick/omit call at the use site says what it means and does not
+multiply this package's surface. If a consumer needs a field that does not exist
+yet, add it here first, then derive.
+
+## Changing a schema is a fourteen-repo change
+
+The consumers on v2 are: admin, common, content, email, group, jobs, marketing,
+page, sitemap, svelte-ui, taxonomy, user (plus data-processor and notification
+transitively). **nestjs-api and nextjs-web are still pinned to v1 (`^1.0.106`)** and
+are NOT to be bumped casually: that is a breaking major jump needing the tagged
+`@todo SCHEMA-V2-MIGRATION` work, not a version bump. NestJS is decommissioned.
+
+Practical consequences:
+
+- **Adding** an optional field is safe. **Renaming, removing, or tightening** one is
+  not — it will typecheck here and fail in services you did not open.
+- Publish, then update consumers deliberately. There is no workspace linking these;
+  each consumer pins a registry range.
+- During development use **yalc** (`yalc publish` / `yalc push`), not a version bump,
+  so you are not burning versions to test a change. `pnpm dev` already runs
+  `tsup --watch --onSuccess "yalc publish --push"`.
+
+## Enum casing is load-bearing
+
+Enum string values are consumed as literals across services and stored in Mongo, so
+their casing is data, not style. Group `managedBy` / `visibility` / `status` are
+**lowercase** (`system`, `private`, `archived`), as are `SavedSearchStatus` and
+`JobAlertFrequency`. Changing a case is a data migration, not a refactor —
+existing documents will silently stop matching.
+
+## The consent fields are a compliance surface
+
+Three shapes here decide whether the platform may mail someone, and each behaves
+differently on purpose:
+
+- **`notificationPrefs`** (`user.schema.ts`) — per-channel, opt-**out**. The
+  consumer reads `!== false`, so a user whose document predates the field must
+  read as *enabled*. That is why adding it needed no backfill migration, and why
+  a "tidy-up" that made the fields required would silently mute every legacy user.
+- **`marketingConsent.subscribed`** — opt-**in**, read as `=== true`. The exact
+  inverse. Do not collapse the two into one shape; they have different legal
+  footing, which email-service's footer rules already encode.
+- **`marketingConsent.jobAlertFrequency`** — a *second* gate on job-alert mail
+  only, so a user can stop alerts while staying subscribed generally.
+
+`NotificationChannel` values are duplicated as a string union in `@thejob/notify`
+(so that package stays dependency-free). This package remains the source of
+truth; adding a channel means editing the enum, the `notificationPrefs` object
+keys, its `.default()`, and that union.
+
+Full picture: `thejob-notification-service/NOTIFICATIONS.md`.
+
+## Conventions
+
+- One module per domain (`user/`, `job/`, `group/`, …), each exporting its schema and
+  its constants, re-exported from `src/index.ts`.
+- Types are derived from schemas (`yup.InferType`), never declared alongside them —
+  a hand-written type that drifts from its schema is the failure this package exists
+  to prevent.