@thejob/schema 2.0.0 → 2.0.1

package/src/user/user-job-preferences.schema.ts

@@ -27,7 +27,7 @@ export const UserJobPreferencesSchema = object({
   /**
    * Whether the job seeker is openly signalling availability. Surfaces the
    * "Open to work" badge on the public profile and boosts visibility in
-   * recruiter search. Defaults to `false` — users must opt in.
+   * recruiter search. Defaults to `false` - users must opt in.
    */
   openToWork: boolean().default(false).label("Open to Work"),
 
@@ -57,7 +57,7 @@ export const UserJobPreferencesSchema = object({
    * (up to 2) for borderline candidates.
    *
    * Distinct from the singular `experienceLevel` field on `UserSchema`
-   * (concat'd via `UserGeneralDetailSchema`) — that field captures the user's
+   * (concat'd via `UserGeneralDetailSchema`) - that field captures the user's
    * own current seniority, while these are the levels they want to *target*.
    * Both reuse the same `ExperienceLevel` taxonomy from `common.constant.ts`
    * so search/match logic doesn't have to translate between two vocabularies.
@@ -70,7 +70,7 @@ export const UserJobPreferencesSchema = object({
     .label("Target Experience Levels"),
 
   /**
-   * Specializations the user is searching for — free-form titles.
+   * Specializations the user is searching for - free-form titles.
    *
    * Job titles are an open vocabulary (think O*NET, ESCO, LinkedIn's title
    * graph), so the schema only enforces length bounds per entry. The wizard
@@ -86,7 +86,7 @@ export const UserJobPreferencesSchema = object({
   /**
    * Minimum acceptable annual base salary, in `minSalaryCurrency`.
    * Stored as an integer in the currency's major unit (e.g. dollars, not cents).
-   * Defaults to 0 ("any salary") rather than being optional — every job-seeker
+   * Defaults to 0 ("any salary") rather than being optional - every job-seeker
    * has a floor, even if it's zero.
    */
   minSalary: number()
@@ -113,7 +113,7 @@ export const UserJobPreferencesSchema = object({
 
   /**
    * Resumes the user has uploaded. Embedded directly on the user document
-   * (capped at 5) — they're cheap to denormalize, every wizard step that
+   * (capped at 5) - they're cheap to denormalize, every wizard step that
    * cares about them is already loading the user doc, and the cap keeps the
    * subdoc bounded.
    *
@@ -121,13 +121,13 @@ export const UserJobPreferencesSchema = object({
    * the API can sign for download is kept here.
    *
    * Distinct from the `Resumes` collection used by the (currently unused)
-   * AI resume-builder flow — onboarding uploads land here, AI-built resumes
+   * AI resume-builder flow - onboarding uploads land here, AI-built resumes
    * live in their own collection.
    */
   resumes: array()
     .of(
       object({
-        // Stable id assigned on upload — used to address a specific entry
+        // Stable id assigned on upload - used to address a specific entry
         // for delete / set-primary operations without exposing the GCS URL
         // as a route key.
         id: string().required().label("ID"),
@@ -157,18 +157,18 @@ export const UserJobPreferencesSchema = object({
 
   /**
    * Parser-suggested values for wizard fields, written by the resume-upload
-   * flow. Every parser-derived field lands here — including profile-shaped
+   * flow. Every parser-derived field lands here - including profile-shaped
    * fields (headline, aboutMe, mobile, location, experienceLevel,
-   * socialAccounts, workExperiences, educations) — so nothing reaches the
+   * socialAccounts, workExperiences, educations) - so nothing reaches the
    * top-level user document until the user confirms it on the matching
    * wizard step. When a user clicks Next on a step, the API drops the
    * matching key from this sub-doc so a re-uploaded resume can't overwrite
    * confirmed answers.
    *
-   * READ RULE — strict:
+   * READ RULE - strict:
    *   `pendingPrefill.<field>` is ONLY for seeding a wizard step's form
    *   initial value (e.g. `prefer(user.<field>, user.pendingPrefill?.<field>)`
-   *   in a step's `load`). It is NOT the user's actual value — it's an
+   *   in a step's `load`). It is NOT the user's actual value - it's an
    *   unconfirmed suggestion. Never substitute it as a fallback in profile
    *   pages, search/match, recommendations, public profile, dashboards, or
    *   APIs. If `user.<field>` is empty there, the correct behavior is empty,

package/src/user/user-recruiter-profile.schema.ts

@@ -26,7 +26,7 @@ export const RecruiterPageLinkSchema = object({
 
 /**
  * Recruiter-role-specific fields on UserSchema. All optional at the field
- * level — presence is gated by `UserRole.Recruiter` in the user's `roles`,
+ * level - presence is gated by `UserRole.Recruiter` in the user's `roles`,
  * not by schema branching, so the user shape stays flat.
  */
 export const UserRecruiterProfileSchema = object({

package/src/user/user.constant.ts

@@ -68,7 +68,7 @@ export enum JobSearchUrgency {
 export const SupportedJobSearchUrgencies = Object.values(JobSearchUrgency);
 
 /**
- * How the user heard about the platform — captured at the end of onboarding
+ * How the user heard about the platform - captured at the end of onboarding
  * for marketing attribution.
  */
 export enum ReferralSource {