@forwardslashns/taskit-validation-messages 1.1.0 → 1.2.0

package/dist/validation/features/client.validation-messages.js

@@ -0,0 +1,389 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CLIENT = void 0;
+exports.CLIENT = {
+    INVALID_REQUEST: {
+        message: 'Missing client id in request',
+        affectedFields: [],
+    },
+    ID_DOES_NOT_EXIST: {
+        message: `Client with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['clientId'],
+    },
+    ACCOUNT_ID_DOES_NOT_EXIST: {
+        message: `Account id with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['accountId'],
+    },
+    FILING_CATEGORY_ID_DOES_NOT_EXIST: {
+        message: `Filing category with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['filingCategoryId'],
+    },
+    FILING_TYPE_ID_DOES_NOT_EXIST: {
+        message: `Parent/Sub status with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['filingTypeId'],
+    },
+    FILING_TYPE_PARENT_REQUIRED: {
+        message: `Parent needs to be specified for filing type 'Files under parent'`,
+        affectedFields: ['parentClientId'],
+    },
+    CURRENT_FILING_TYPE_PARENT_REQUIRED: {
+        message: `Parent needs to be specified for current filing type 'Files under parent'`,
+        affectedFields: ['parentClientId'],
+    },
+    STATE_ID_DOES_NOT_EXIST: {
+        message: `State with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['stateId'],
+    },
+    BUSINESS_ACTIVITY_ID_DOES_NOT_EXIST: {
+        message: `Business activity with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['businessActivityId'],
+    },
+    BILLING_TYPE_ID_DOES_NOT_EXIST: {
+        message: `Billing type with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['billingTypeId'],
+    },
+    ENTITY_TYPE_ID_DOES_NOT_EXIST: {
+        message: `Entity type with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['entityTypeId'],
+    },
+    CLIENT_WITH_SAME_FEDERAL_LEGAL_ID_EXISTS: {
+        message: `This ID is already in use. Please enter a different ID.`,
+        affectedFields: ['federalLegalId'],
+    },
+    INVALID_CLIENT_ACTIVITY_STATUS: {
+        message: `The 'Is active' field only applies to our clients. Please update the client type to 'Not our client' or update the 'Is active' status to 'Active'.`,
+        affectedFields: ['isActive', 'clientType'],
+    },
+    INVALID_FEDERAL_LEGAL_ID: {
+        message: `Enter a valid {legalIdType} (e.g. {legalIdValue})`,
+        params: ['legalIdType', 'legalIdValue'],
+        affectedFields: ['federalLegalId'],
+    },
+    NAME_ALREADY_EXISTS: {
+        message: `Client with the same name '{name}' already exists`,
+        params: ['name'],
+        affectedFields: ['name'],
+    },
+    NOT_ALIGNED_DATE_ESTABLISHED_ENTITY_TYPE_STARTING_DATE: {
+        message: `One or more entity types have a start date that is before the client's date established, {clientDateEstablished}. ({entityType} starting {entityTypeStartingDate}). Please update the entity type start dates to be on or after the client's date established, or update the client's date established.`,
+        params: ['clientDateEstablished', 'entityType', 'entityTypeStartingDate'],
+        affectedFields: ['dateEstablished', 'entityTypes'],
+    },
+    NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
+        message: `The Parent/Sub status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Parent/Sub status or the client's date established.`,
+        params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
+        affectedFields: ['dateEstablished', 'filingTypes'],
+    },
+    NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
+        message: `The state, {domesticState}, starts on {domesticStateStartingDate}, which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the state or the client's date established.`,
+        params: ['clientDateEstablished', 'domesticState', 'domesticStateStartingDate'],
+        affectedFields: ['dateEstablished', 'domesticStates'],
+    },
+    NOT_ALIGNED_DATE_ESTABLISHED_CLOSE_DATE: {
+        message: `Adjust the close date to be after the date established.`,
+        affectedFields: ['dateEstablished', 'closeDate'],
+    },
+    NOT_ALIGNED_CLOSE_DATE_ENTITY_TYPE_STARTING_DATE: {
+        message: `One or more entity types have start dates that are after the client's close date, {clientCloseDate}. {entityType} starting {entityTypeStartingDate}. Please update the entity type/s end date/s to be on or before the client's close date, or update the client's close date.`,
+        params: ['clientCloseDate', 'entityType', 'entityTypeStartingDate'],
+        affectedFields: ['closeDate', 'entityTypes'],
+    },
+    NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
+        message: `One or more Parent/Sub status have a start date which is after the client's close date of {clientCloseDate}. {filingType}, starting {filingTypeStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
+        params: ['clientCloseDate', 'filingType', 'filingTypeStartingDate'],
+        affectedFields: ['closeDate', 'filingTypes'],
+    },
+    ENTITY_TYPE_STARTING_DATE_NOT_POPULATED: {
+        message: `Current Entity Type Starting Date cannot be Empty`,
+        affectedFields: ['entityTypeStartingDate'],
+    },
+    FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
+        message: `Current Parent/Sub status Starting Date cannot be Empty`,
+        affectedFields: ['filingTypeStartingDate'],
+    },
+    DOMESTIC_STATE_STARTING_DATE_NOT_POPULATED: {
+        message: `Current Domestic State Starting Date cannot be Empty`,
+        affectedFields: ['domesticStateStartingDate'],
+    },
+    NOT_ALIGNED_ENTITY_TYPE_STARTING_ENDING_DATE: {
+        message: `Entity type starting date needs to be before the ending date`,
+        affectedFields: ['entityTypeStartingDate', 'entityTypeEndingDate'],
+    },
+    NOT_ALIGNED_FILING_TYPE_STARTING_ENDING_DATE: {
+        message: `Parent/Sub status starting date needs to be before the ending date`,
+        affectedFields: ['filingTypeStartingDate', 'filingTypeEndingDate'],
+    },
+    NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
+        message: `One or more states have a start date which is after the client's close date of {clientCloseDate}. {domesticState} starting {domesticStateStartingDate}. Please update the state/s start date/s to be before the client's close date, or update the client's close date.`,
+        params: ['clientCloseDate', 'domesticState', 'domesticStateStartingDate'],
+        affectedFields: ['closeDate', 'domesticStates'],
+    },
+    CLIENT_COULD_NOT_BE_LOCKED_WITHOUT_ACCOUNT_ID: {
+        message: `Choose an Account ID`,
+        affectedFields: ['accountId'],
+    },
+    CLIENT_COULD_NOT_BE_LOCKED_WITHOUT_BUSINESS_ACTIVITY_ID: {
+        message: `Choose a Business Activity`,
+        affectedFields: ['businessActivityId'],
+    },
+    CLIENT_COULD_NOT_BE_LOCKED_WITHOUT_BILLING_TYPE_ID: {
+        message: `Choose a Billing Type`,
+        affectedFields: ['billingTypeId'],
+    },
+    CLIENT_COULD_NOT_BE_LOCKED_WITHOUT_FILING_CATEGORY_ID: {
+        message: `Choose a Filing Category`,
+        affectedFields: ['filingCategoryId'],
+    },
+    CLIENT_COULD_NOT_BE_LOCKED_WITHOUT_CONTACT: {
+        message: `Create a Contact - One contact needs to have been saved to this client`,
+        affectedFields: ['contacts'],
+    },
+    CLIENT_COULD_NOT_BE_LOCKED_WITHOUT_ADDRESS: {
+        message: `Create an Address - One address needs to have been saved to this client`,
+        affectedFields: ['addresses'],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_CLIENT_RELATIONSHIP_EXIST: {
+        message: `This client cannot be deleted because it has client relationships associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_CLIENT_PROJECT_TEMPLATES_EXIST: {
+        message: `This client cannot be deleted because it has client project templates associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_ADDITIONAL_INFORMATION_EXIST: {
+        message: `This client cannot be deleted because it has additional information associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_BANK_ACCOUNTS_EXIST: {
+        message: `This client cannot be deleted because it has bank accounts associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_CREDIT_CARDS_EXIST: {
+        message: `This client cannot be deleted because it has credit cards associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_WORKLOGS_EXIST: {
+        message: `This client cannot be deleted because it has worklogs associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_INVOICES_EXIST: {
+        message: `This client cannot be deleted because it has invoices associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_PAYMENTS_EXIST: {
+        message: `This client cannot be deleted because it has payments associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_DOCUMENTS_EXIST: {
+        message: `This client cannot be deleted because it has documents associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_JOURNALS_EXIST: {
+        message: `This client cannot be deleted because it has journals associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_FUTURES_EXIST: {
+        message: `This client cannot be deleted because it has futures associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_PROJECTS_EXIST: {
+        message: `This client cannot be deleted because it has projects associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_TASKS_EXIST: {
+        message: `This client cannot be deleted because it has tasks associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_ADDRESSES_EXIST: {
+        message: `This client cannot be deleted because it has addresses associated`,
+        affectedFields: [],
+    },
+    CLIENT_COULD_NOT_BE_DELETED_CONTACTS_EXIST: {
+        message: `This client cannot be deleted because it has contacts associated`,
+        affectedFields: [],
+    },
+    ENTITY_TYPES_IDS_DOES_NOT_EXIST: {
+        message: `Entity types with ids '{ids}' do not exist`,
+        params: ['ids'],
+        affectedFields: ['entityTypeId'],
+    },
+    AT_LEAST_ONE_ENTITY_TYPE_SHOULD_EXIST: {
+        message: `At least one entity type should exist`,
+        affectedFields: ['entityTypes'],
+    },
+    ENTITY_TYPES_STARTING_DATE_NOT_POPULATED: {
+        message: `Starting date for {entityType} cannot be empty`,
+        params: ['entityType'],
+        affectedFields: ['entityTypeStartingDate'],
+    },
+    NOT_ALIGNED_ENTITY_TYPES_STARTING_ENDING_DATE: {
+        message: `The ending date for {entityType} must be after its starting date`,
+        params: ['entityType'],
+        affectedFields: ['entityTypeStartingDate', 'entityTypeEndingDate'],
+    },
+    NOT_ALIGNED_DATE_ESTABLISHED_ENTITY_TYPES_STARTING_DATE: {
+        message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
+        params: ['clientStartDate'],
+        affectedFields: ['entityTypeStartingDate', 'dateEstablished'],
+    },
+    NOT_ALIGNED_CLOSE_DATE_ENTITY_TYPES_STARTING_DATE: {
+        message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
+        params: ['clientCloseDate'],
+        affectedFields: ['entityTypeStartingDate', 'closeDate'],
+    },
+    ENTITY_TYPES_DATE_GAP_DETECTED: {
+        message: `There is a gap in the timeframes between {currentEntityType}, ending {currentEntityTypeEndDate}, and {nextEntityType}, starting {nextEntityTypeStartDate}. Please adjust the dates to fill this gap.`,
+        params: ['currentEntityType', 'currentEntityTypeEndDate', 'nextEntityType', 'nextEntityTypeStartDate'],
+        affectedFields: ['entityTypes'],
+    },
+    ENTITY_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
+        message: `There are two entries for {entityType} with timeframes that immediately follow each other. {entityType} ending {firstPeriodEnd}, and {entityType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {entityType}. `,
+        params: ['entityType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
+        affectedFields: ['entityTypes'],
+    },
+    ENTITY_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
+        message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first entity type ({earliestEntityType} starting {earliestEntityTypeStartDate}). There must be an entity type that begins on {dateEstablished}.`,
+        params: ['dateEstablished', 'earliestEntityType', 'earliestEntityTypeStartDate'],
+        affectedFields: ['entityTypes', 'dateEstablished'],
+    },
+    ENTITY_TYPES_DATES_OVERLAP: {
+        message: `The client already has {entityType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
+        params: ['entityType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
+        affectedFields: ['entityTypes'],
+    },
+    ALL_NON_LAST_ENTITY_TYPES_REQUIRE_ENDING_DATE: {
+        message: `Only the last entity type can be open without an end date. Add an ending date to the existing entity type before adding a start date for a new entity type.`,
+        affectedFields: ['entityTypeEndingDate'],
+    },
+    CURRENT_ENTITY_TYPE_CANNOT_HAVE_ENDING_DATE: {
+        message: `The current entity type cannot have an end date. Please remove the end date for this state.`,
+        affectedFields: ['entityTypeEndingDate'],
+    },
+    FILING_TYPES_IDS_DOES_NOT_EXIST: {
+        message: `Parent/Sub status with ids '{ids}' do not exist`,
+        params: ['ids'],
+        affectedFields: ['filingTypeId'],
+    },
+    AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
+        message: `At least one Parent/Sub status should exist`,
+        affectedFields: ['filingTypes'],
+    },
+    FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
+        message: `Starting date for {filingType} cannot be empty`,
+        params: ['filingType'],
+        affectedFields: ['filingTypeStartingDate'],
+    },
+    NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
+        message: `The ending date for {filingType} must be after its starting date`,
+        params: ['filingType'],
+        affectedFields: ['filingTypeStartingDate', 'filingTypeEndingDate'],
+    },
+    NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
+        message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
+        params: ['clientStartDate'],
+        affectedFields: ['filingTypeStartingDate', 'dateEstablished'],
+    },
+    NOT_ALIGNED_CLOSE_DATE_FILING_TYPES_STARTING_DATE: {
+        message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
+        params: ['clientCloseDate'],
+        affectedFields: ['filingTypeStartingDate', 'closeDate'],
+    },
+    FILING_TYPES_DATE_GAP_DETECTED: {
+        message: `There is a gap in the timeframes between {currentFilingType}, ending {currentFilingTypeEndDate}, and {nextFilingType}, starting {nextFilingTypeStartDate}. Please adjust the dates to fill this gap.`,
+        params: ['currentFilingType', 'currentFilingTypeEndDate', 'nextFilingType', 'nextFilingTypeStartDate'],
+        affectedFields: ['filingTypes'],
+    },
+    FILING_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
+        message: `There are two entries for {filingType} with timeframes that immediately follow each other. {filingType} ending {firstPeriodEnd}, and {filingType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingType}. `,
+        params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
+        affectedFields: ['filingTypes'],
+    },
+    FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
+        message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first Parent/Sub status ({earliestFilingType} starting {earliestFilingTypeStartDate}). There must be a Parent/Sub status that begins on {dateEstablished}.`,
+        params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
+        affectedFields: ['filingTypes', 'dateEstablished'],
+    },
+    FILING_TYPES_DATES_OVERLAP: {
+        message: `The client already has {filingType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
+        params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
+        affectedFields: ['filingTypes'],
+    },
+    ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
+        message: `Only the last Parent/Sub status can be open without an end date. Add an ending date to the existing Parent/Sub status before adding a start date for a new Parent/Sub status.`,
+        affectedFields: ['filingTypeEndingDate'],
+    },
+    CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
+        message: `The current Parent/Sub status cannot have an end date. Please remove the end date for this state.`,
+        affectedFields: ['filingTypeEndingDate'],
+    },
+    STATES_IDS_DOES_NOT_EXIST: {
+        message: `States with ids '{ids}' do not exist`,
+        params: ['ids'],
+        affectedFields: ['stateId'],
+    },
+    RESIDENCE_TYPE_DOES_NOT_EXIST: {
+        message: `Residence type with ids '{ids}' does not exist`,
+        params: ['ids'],
+        affectedFields: ['residenceTypeId'],
+    },
+    AT_LEAST_ONE_DOMESTIC_STATE_SHOULD_EXIST: {
+        message: `At least one domestic state should exist`,
+        affectedFields: ['domesticStates'],
+    },
+    STATES_STARTING_DATE_NOT_POPULATED: {
+        message: `Starting date for {state} cannot be empty`,
+        params: ['state'],
+        affectedFields: ['stateStartingDate'],
+    },
+    NOT_ALIGNED_STATES_STARTING_ENDING_DATE: {
+        message: `The ending date for {state} must be after its starting date`,
+        params: ['state'],
+        affectedFields: ['stateStartingDate', 'stateEndingDate'],
+    },
+    NOT_ALIGNED_DATE_ESTABLISHED_STATES_STARTING_DATE: {
+        message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
+        params: ['clientStartDate'],
+        affectedFields: ['stateStartingDate', 'dateEstablished'],
+    },
+    NOT_ALIGNED_CLOSE_DATE_STATES_STARTING_DATE: {
+        message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
+        params: ['clientCloseDate'],
+        affectedFields: ['stateStartingDate', 'closeDate'],
+    },
+    DOMESTIC_STATES_DATE_GAP_DETECTED: {
+        message: `There is a gap in the timeframes between {currentState}, ending {currentStateEndDate}, and {nextState}, starting {nextStateStartDate}. Please adjust the dates to fill this gap.`,
+        params: ['currentState', 'currentStateEndDate', 'nextState', 'nextStateStartDate'],
+        affectedFields: ['domesticStates'],
+    },
+    STATES_CONSECUTIVE_DUPLICATES_DETECTED: {
+        message: `There are two entries for {state} with timeframes that immediately follow each other. {state} ending {firstPeriodEnd}, and {state} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {state}. `,
+        params: ['state', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
+        affectedFields: ['domesticStates'],
+    },
+    DOMESTIC_STATE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
+        message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first state ({earliestState} starting {earliestStateStartDate}). There must be a state that begins on {dateEstablished}.`,
+        params: ['dateEstablished', 'earliestState', 'earliestStateStartDate'],
+        affectedFields: ['domesticStates', 'dateEstablished'],
+    },
+    STATES_DATES_OVERLAP: {
+        message: `The client already has {state} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
+        params: ['state', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
+        affectedFields: ['domesticStates'],
+    },
+    ALL_NON_LAST_DOMESTIC_STATES_REQUIRE_ENDING_DATE: {
+        message: `Only the last domestic state can be open without an end date. Add an ending date to the existing state before adding a start date for a new state.`,
+        affectedFields: ['stateEndingDate'],
+    },
+    CURRENT_DOMESTIC_STATE_CANNOT_HAVE_ENDING_DATE: {
+        message: `The current domestic state cannot have an end date. Please remove the end date for this state.`,
+        affectedFields: ['stateEndingDate'],
+    },
+};

package/dist/validation/features/commission-detail.validation-messages.d.ts

@@ -0,0 +1,24 @@
+export declare const COMISSION_DETAIL: {
+    readonly INVALID_REQUEST_IS_SUBJECT_TO_COMMISSION: {
+        readonly message: "If client is subject to commission, sales representative and commission rate must be provided.";
+        readonly affectedFields: readonly ["isSubjectToCommission", "salesRepresentativeId", "commissionRate"];
+    };
+    readonly INVALID_REQUEST_IS_NOT_SUBJECT_TO_COMMISSION: {
+        readonly message: "If client is not subject to commission, sales representative and commission rate must not be provided.";
+        readonly affectedFields: readonly ["isSubjectToCommission", "salesRepresentativeId", "commissionRate"];
+    };
+    readonly SALES_REPRESENTATIVE_DOES_NOT_EXIST: {
+        readonly message: "Sales representative with id '{id}' does not exist";
+        readonly params: readonly ["id"];
+        readonly affectedFields: readonly ["salesRepresentativeId"];
+    };
+    readonly COMISSION_RATE_TOO_LOW: {
+        readonly message: "Enter a commission value greater than 0.0";
+        readonly affectedFields: readonly ["commissionRate"];
+    };
+    readonly COMISSION_RATE_TOO_HIGH: {
+        readonly message: "Enter a value less than 100%.";
+        readonly affectedFields: readonly ["commissionRate"];
+    };
+};
+//# sourceMappingURL=commission-detail.validation-messages.d.ts.map

package/dist/validation/features/commission-detail.validation-messages.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"commission-detail.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/commission-detail.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB;;;;;;;;;;;;;;;;;;;;;;CAsBnB,CAAC"}

package/dist/validation/features/commission-detail.validation-messages.js

@@ -0,0 +1,26 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.COMISSION_DETAIL = void 0;
+exports.COMISSION_DETAIL = {
+    INVALID_REQUEST_IS_SUBJECT_TO_COMMISSION: {
+        message: 'If client is subject to commission, sales representative and commission rate must be provided.',
+        affectedFields: ['isSubjectToCommission', 'salesRepresentativeId', 'commissionRate'],
+    },
+    INVALID_REQUEST_IS_NOT_SUBJECT_TO_COMMISSION: {
+        message: 'If client is not subject to commission, sales representative and commission rate must not be provided.',
+        affectedFields: ['isSubjectToCommission', 'salesRepresentativeId', 'commissionRate'],
+    },
+    SALES_REPRESENTATIVE_DOES_NOT_EXIST: {
+        message: `Sales representative with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['salesRepresentativeId'],
+    },
+    COMISSION_RATE_TOO_LOW: {
+        message: `Enter a commission value greater than 0.0`,
+        affectedFields: ['commissionRate'],
+    },
+    COMISSION_RATE_TOO_HIGH: {
+        message: `Enter a value less than 100%.`,
+        affectedFields: ['commissionRate'],
+    },
+};

package/dist/validation/features/contact.validation-messages.d.ts

@@ -0,0 +1,37 @@
+export declare const CONTACT: {
+    readonly CONTACT_ROLES_NOT_FOUND: {
+        readonly message: "Contact roles with ids {ids} do not exist";
+        readonly params: readonly ["ids"];
+        readonly affectedFields: readonly ["contactRoleId"];
+    };
+    readonly CONTACT_TYPES_NOT_FOUND: {
+        readonly message: "Contact types with ids {ids} do not exist";
+        readonly params: readonly ["ids"];
+        readonly affectedFields: readonly ["contactTypeId"];
+    };
+    readonly LEGAL_CONTACT_MUST_BE_PROVIDED: {
+        readonly message: "The client must have a legal contact. Please set the contact type to 'Legal'.";
+        readonly affectedFields: readonly ["contacts"];
+    };
+    readonly MULTIPLE_LEGAL_CONTACTS_PROVIDED: {
+        readonly message: "The client must have only one legal contact. Please ensure only one contact is set to 'Legal'.";
+        readonly affectedFields: readonly ["contacts"];
+    };
+    readonly BILLING_CONTACT_MUST_BE_PROVIDED: {
+        readonly message: "The client must have a billing contact. Please set the contact type to 'Billing'.";
+        readonly affectedFields: readonly ["contacts"];
+    };
+    readonly MULTIPLE_BILLING_CONTACTS_PROVIDED: {
+        readonly message: "The client must have only one billing contact. Please ensure only one contact is set to 'Billing'.";
+        readonly affectedFields: readonly ["contacts"];
+    };
+    readonly PRIMARY_CONTACT_MUST_BE_PROVIDED: {
+        readonly message: "The client must have a primary contact. Please set the contact type to 'Primary'.";
+        readonly affectedFields: readonly ["contacts"];
+    };
+    readonly MULTIPLE_PRIMARY_CONTACTS_PROVIDED: {
+        readonly message: "The client must have only one primary contact. Please ensure only one contact is set to 'Primary'.";
+        readonly affectedFields: readonly ["contacts"];
+    };
+};
+//# sourceMappingURL=contact.validation-messages.d.ts.map

package/dist/validation/features/contact.validation-messages.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"contact.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/contact.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmCV,CAAC"}

package/dist/validation/features/contact.validation-messages.js

@@ -0,0 +1,39 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CONTACT = void 0;
+exports.CONTACT = {
+    CONTACT_ROLES_NOT_FOUND: {
+        message: `Contact roles with ids {ids} do not exist`,
+        params: ['ids'],
+        affectedFields: ['contactRoleId'],
+    },
+    CONTACT_TYPES_NOT_FOUND: {
+        message: `Contact types with ids {ids} do not exist`,
+        params: ['ids'],
+        affectedFields: ['contactTypeId'],
+    },
+    LEGAL_CONTACT_MUST_BE_PROVIDED: {
+        message: `The client must have a legal contact. Please set the contact type to 'Legal'.`,
+        affectedFields: ['contacts'],
+    },
+    MULTIPLE_LEGAL_CONTACTS_PROVIDED: {
+        message: `The client must have only one legal contact. Please ensure only one contact is set to 'Legal'.`,
+        affectedFields: ['contacts'],
+    },
+    BILLING_CONTACT_MUST_BE_PROVIDED: {
+        message: `The client must have a billing contact. Please set the contact type to 'Billing'.`,
+        affectedFields: ['contacts'],
+    },
+    MULTIPLE_BILLING_CONTACTS_PROVIDED: {
+        message: `The client must have only one billing contact. Please ensure only one contact is set to 'Billing'.`,
+        affectedFields: ['contacts'],
+    },
+    PRIMARY_CONTACT_MUST_BE_PROVIDED: {
+        message: `The client must have a primary contact. Please set the contact type to 'Primary'.`,
+        affectedFields: ['contacts'],
+    },
+    MULTIPLE_PRIMARY_CONTACTS_PROVIDED: {
+        message: `The client must have only one primary contact. Please ensure only one contact is set to 'Primary'.`,
+        affectedFields: ['contacts'],
+    },
+};

package/dist/validation/features/credit-card.validation-messages.d.ts

@@ -0,0 +1,11 @@
+export declare const CREDIT_CARD: {
+    readonly INVALID_EXPIRATION_DATE: {
+        readonly message: "Enter a valid expiration date (i.e. 12/2024).";
+        readonly affectedFields: readonly ["expirationDate"];
+    };
+    readonly INVALID_SECURITY_CODE: {
+        readonly message: "Enter a valid security code (i.e. 1234).";
+        readonly affectedFields: readonly ["securityCode"];
+    };
+};
+//# sourceMappingURL=credit-card.validation-messages.d.ts.map

package/dist/validation/features/credit-card.validation-messages.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"credit-card.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/credit-card.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,WAAW;;;;;;;;;CASd,CAAC"}

package/dist/validation/features/credit-card.validation-messages.js

@@ -0,0 +1,13 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CREDIT_CARD = void 0;
+exports.CREDIT_CARD = {
+    INVALID_EXPIRATION_DATE: {
+        message: 'Enter a valid expiration date (i.e. 12/2024).',
+        affectedFields: ['expirationDate'],
+    },
+    INVALID_SECURITY_CODE: {
+        message: 'Enter a valid security code (i.e. 1234).',
+        affectedFields: ['securityCode'],
+    },
+};

package/dist/validation/features/data-filter.validation-messages.d.ts

@@ -0,0 +1,19 @@
+export declare const DATA_FILTER: {
+    readonly MISSING_PAGE_SIZE: {
+        readonly message: "Request is invalid, 'pageSize' must exist if 'pageNumber' exists";
+        readonly affectedFields: readonly ["pageSize"];
+    };
+    readonly MISSING_PAGE_NUMBER: {
+        readonly message: "Request is invalid, 'pageNumber' must exist if 'pageSize' exists";
+        readonly affectedFields: readonly ["pageNumber"];
+    };
+    readonly MISSING_SORT_BY: {
+        readonly message: "Request is invalid, 'sortBy' must exist if 'sortType' exists";
+        readonly affectedFields: readonly ["sortBy"];
+    };
+    readonly MISSING_SORT_TYPE: {
+        readonly message: "Request is invalid, 'sortType' must exist if 'sortBy' exists";
+        readonly affectedFields: readonly ["sortType"];
+    };
+};
+//# sourceMappingURL=data-filter.validation-messages.d.ts.map

package/dist/validation/features/data-filter.validation-messages.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"data-filter.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/data-filter.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,WAAW;;;;;;;;;;;;;;;;;CAiBd,CAAC"}

package/dist/validation/features/data-filter.validation-messages.js

@@ -0,0 +1,21 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DATA_FILTER = void 0;
+exports.DATA_FILTER = {
+    MISSING_PAGE_SIZE: {
+        message: `Request is invalid, 'pageSize' must exist if 'pageNumber' exists`,
+        affectedFields: ['pageSize'],
+    },
+    MISSING_PAGE_NUMBER: {
+        message: `Request is invalid, 'pageNumber' must exist if 'pageSize' exists`,
+        affectedFields: ['pageNumber'],
+    },
+    MISSING_SORT_BY: {
+        message: `Request is invalid, 'sortBy' must exist if 'sortType' exists`,
+        affectedFields: ['sortBy'],
+    },
+    MISSING_SORT_TYPE: {
+        message: `Request is invalid, 'sortType' must exist if 'sortBy' exists`,
+        affectedFields: ['sortType'],
+    },
+};

package/dist/validation/features/filing-category.validation-messages.d.ts

@@ -0,0 +1,21 @@
+export declare const FILING_CATEGORY: {
+    readonly INVALID_REQUEST: {
+        readonly message: "Missing filing category id in request";
+        readonly affectedFields: readonly [];
+    };
+    readonly ID_DOES_NOT_EXIST: {
+        readonly message: "Filing category with id '{id}' does not exist";
+        readonly params: readonly ["id"];
+        readonly affectedFields: readonly ["filingCategoryId"];
+    };
+    readonly NAME_ALREADY_EXISTS: {
+        readonly message: "Filing category with the same name '{name}' already exists";
+        readonly params: readonly ["name"];
+        readonly affectedFields: readonly ["name"];
+    };
+    readonly OPTION_IN_USE: {
+        readonly message: "This option is currently in use and cannot be deleted.";
+        readonly affectedFields: readonly [];
+    };
+};
+//# sourceMappingURL=filing-category.validation-messages.d.ts.map

package/dist/validation/features/filing-category.validation-messages.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"filing-category.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/filing-category.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,eAAe;;;;;;;;;;;;;;;;;;;CAmBlB,CAAC"}

package/dist/validation/features/filing-category.validation-messages.js

@@ -0,0 +1,23 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.FILING_CATEGORY = void 0;
+exports.FILING_CATEGORY = {
+    INVALID_REQUEST: {
+        message: 'Missing filing category id in request',
+        affectedFields: [],
+    },
+    ID_DOES_NOT_EXIST: {
+        message: `Filing category with id '{id}' does not exist`,
+        params: ['id'],
+        affectedFields: ['filingCategoryId'],
+    },
+    NAME_ALREADY_EXISTS: {
+        message: `Filing category with the same name '{name}' already exists`,
+        params: ['name'],
+        affectedFields: ['name'],
+    },
+    OPTION_IN_USE: {
+        message: `This option is currently in use and cannot be deleted.`,
+        affectedFields: [],
+    },
+};