npm - @forwardslashns/taskit-validation-messages - Versions diffs - 1.10.41 → 1.10.43 - Mend

@forwardslashns/taskit-validation-messages 1.10.41 → 1.10.43

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (51) hide show

package/dist/validation/features/account-categories.validation-messages.js CHANGED Viewed

@@ -16,7 +16,7 @@ exports.ACCOUNT_CATEGORIES = (0, validation_message_types_1.defineValidationFeat
     },
     NAME_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Account category with the same name '{name}' already exists`,
+        message: `Account category with the same name {name} already exists`,
         params: ['name'],
         affectedFields: ['accountCategory'],
     },

package/dist/validation/features/account-ids.validation-messages.js CHANGED Viewed

@@ -16,7 +16,7 @@ exports.ACCOUNT_IDS = (0, validation_message_types_1.defineValidationFeatureMess
     },
     NAME_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Account id with the same name '{name}' already exists`,
+        message: `Account id with the same name {name} already exists`,
         params: ['name'],
         affectedFields: ['accountId'],
     },

package/dist/validation/features/business-activities.validation-messages.js CHANGED Viewed

@@ -16,7 +16,7 @@ exports.BUSINESS_ACTIVITIES = (0, validation_message_types_1.defineValidationFea
     },
     NAME_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Business activity with the same name '{name}' already exists.`,
+        message: `Business activity with the same name {name} already exists.`,
         params: ['name'],
         affectedFields: ['businessActivity'],
     },

package/dist/validation/features/client-current-entity-statuses.validation-messages.js CHANGED Viewed

@@ -50,13 +50,13 @@ exports.CLIENT_CURRENT_ENTITY_STATUS = (0, validation_message_types_1.defineVali
     },
     INVALID_FEDERAL_LEGAL_ID: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Enter a valid federal legal ID '{legalIdType}' (e.g. '{legalIdValue}')`,
+        message: `Enter a valid federal legal ID {legalIdType} (e.g. {legalIdValue})`,
         params: ['legalIdType', 'legalIdValue'],
         affectedFields: ['federalLegalId'],
     },
     NAME_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Client with the same name '{name}' already exists`,
+        message: `Client with the same name {name} already exists`,
         params: ['name'],
         affectedFields: ['name'],
     },
@@ -187,13 +187,13 @@ exports.CLIENT_CURRENT_ENTITY_STATUS = (0, validation_message_types_1.defineVali
     },
     INITIAL_FILING_DATE_BEFORE_DATE_ESTABLISHED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Initial filing date cannot be before date established '{dateEstablished}'. Please adjust the dates to continue.`,
+        message: `Initial filing date cannot be before date established {dateEstablished}. Please adjust the dates to continue.`,
         params: ['dateEstablished'],
         affectedFields: ['initialFilingDate'],
     },
     FINAL_FILING_DATE_BEFORE_INITIAL_FILING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Final filing date cannot be before initial filing date '{initialFilingDate}'. Please adjust the dates to continue.`,
+        message: `Final filing date cannot be before initial filing date {initialFilingDate}. Please adjust the dates to continue.`,
         params: ['initialFilingDate'],
         affectedFields: ['finalFilingDate'],
     },
@@ -204,13 +204,13 @@ exports.CLIENT_CURRENT_ENTITY_STATUS = (0, validation_message_types_1.defineVali
     },
     SERVICE_ENDING_DATE_BEFORE_SERVICE_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Service ending date cannot be before service starting date '{serviceStartingDate}'. Please adjust the dates to continue.`,
+        message: `Service ending date cannot be before service starting date {serviceStartingDate}. Please adjust the dates to continue.`,
         params: ['serviceStartingDate'],
         affectedFields: ['serviceEndingDate'],
     },
     SERVICE_ENDING_DATE_REQUIRED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `'{clientName}' has been serviced since '{serviceStartingDate}' and is no longer our client. Please enter the service ending date.`,
+        message: `{clientName} has been serviced since {serviceStartingDate} and is no longer our client. Please enter the service ending date.`,
         params: ['clientName', 'serviceStartingDate'],
         affectedFields: ['serviceEndingDate'],
     },

package/dist/validation/features/client-records-entity-states-histories.validation-messages.js CHANGED Viewed

@@ -11,13 +11,13 @@ exports.CLIENT_RECORDS_ENTITY_STATES = (0, validation_message_types_1.defineVali
     },
     NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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.`,
+        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', 'domesticState'],
     },
     NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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.`,
+        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', 'domesticState'],
     },
@@ -45,49 +45,49 @@ exports.CLIENT_RECORDS_ENTITY_STATES = (0, validation_message_types_1.defineVali
     },
     STATES_STARTING_DATE_NOT_POPULATED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Starting date for '{state}' cannot be empty`,
+        message: `Starting date for {state} cannot be empty`,
         params: ['state'],
         affectedFields: ['stateStartingDate'],
     },
     NOT_ALIGNED_STATES_STARTING_ENDING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `The ending date for '{state}' must be after its starting 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: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Adjust the start date to be on or after the client's date established, '{clientStartDate}'.`,
+        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: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Adjust the start date to be before the client's close date, '{clientCloseDate}'.`,
+        message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
         params: ['clientCloseDate'],
         affectedFields: ['stateStartingDate', 'closeDate'],
     },
     DOMESTIC_STATES_DATE_GAP_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There is a gap in the timeframes between '{currentState}', ending '{currentStateEndDate}', and '{nextState}', starting '{nextStateStartDate}'. Please adjust the dates to fill this gap.`,
+        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: ['domesticState'],
     },
     STATES_CONSECUTIVE_DUPLICATES_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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}'. `,
+        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: ['domesticState'],
     },
     DOMESTIC_STATE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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}'.`,
+        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: ['domesticState', 'dateEstablished'],
     },
     STATES_DATES_OVERLAP: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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.`,
+        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: ['domesticState'],
     },

package/dist/validation/features/client-records-entity-types-histories.validation-messages.js CHANGED Viewed

@@ -11,13 +11,13 @@ exports.CLIENT_RECORDS_ENTITY_TYPES = (0, validation_message_types_1.defineValid
     },
     NOT_ALIGNED_DATE_ESTABLISHED_ENTITY_TYPE_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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.`,
+        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', 'entityType'],
     },
     NOT_ALIGNED_CLOSE_DATE_ENTITY_TYPE_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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.`,
+        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', 'entityType'],
     },
@@ -44,49 +44,49 @@ exports.CLIENT_RECORDS_ENTITY_TYPES = (0, validation_message_types_1.defineValid
     },
     ENTITY_TYPES_STARTING_DATE_NOT_POPULATED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Starting date for '{entityType}' cannot be empty`,
+        message: `Starting date for {entityType} cannot be empty`,
         params: ['entityType'],
         affectedFields: ['entityTypeStartingDate'],
     },
     NOT_ALIGNED_ENTITY_TYPES_STARTING_ENDING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `The ending date for '{entityType}' must be after its starting 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: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Adjust the start date to be on or after the client's date established, '{clientStartDate}'.`,
+        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: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Adjust the start date to be before the client's close date, '{clientCloseDate}'.`,
+        message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
         params: ['clientCloseDate'],
         affectedFields: ['entityTypeStartingDate', 'closeDate'],
     },
     ENTITY_TYPES_DATE_GAP_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There is a gap in the timeframes between '{currentEntityType}', ending '{currentEntityTypeEndDate}', and '{nextEntityType}', starting '{nextEntityTypeStartDate}'. Please adjust the dates to fill this gap.`,
+        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: ['entityType'],
     },
     ENTITY_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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}'. `,
+        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: ['entityType'],
     },
     ENTITY_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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}'.`,
+        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: ['entityType', 'dateEstablished'],
     },
     ENTITY_TYPES_DATES_OVERLAP: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        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.`,
+        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: ['entityType'],
     },

package/dist/validation/features/client-records-filing-statuses-histories.validation-messages.js CHANGED Viewed

@@ -11,13 +11,13 @@ exports.CLIENT_RECORDS_FILING_STATUSES = (0, validation_message_types_1.defineVa
     },
     NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUS_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `The Sub/Parent status '{filingStatus}' starts on '{filingStatusStartingDate}' which is earlier than the client's date established, '{clientDateEstablished}'. Please adjust the start date of the Sub/Parent status or the client's date established.`,
+        message: `The Sub/Parent status {filingStatus} starts on {filingStatusStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.`,
         params: ['clientDateEstablished', 'filingStatus', 'filingStatusStartingDate'],
         affectedFields: ['dateEstablished', 'filingStatus'],
     },
     NOT_ALIGNED_CLOSE_DATE_FILING_STATUS_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `One or more Sub/Parent status have a start date which is after the client's close date of '{clientCloseDate}'. '{filingStatus}', starting '{filingStatusStartingDate}'. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
+        message: `One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {filingStatus}, starting {filingStatusStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
         params: ['clientCloseDate', 'filingStatus', 'filingStatusStartingDate'],
         affectedFields: ['closeDate', 'filingStatus'],
     },
@@ -44,49 +44,49 @@ exports.CLIENT_RECORDS_FILING_STATUSES = (0, validation_message_types_1.defineVa
     },
     FILING_STATUSES_STARTING_DATE_NOT_POPULATED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Starting date for '{filingStatus}' cannot be empty`,
+        message: `Starting date for {filingStatus} cannot be empty`,
         params: ['filingStatus'],
         affectedFields: ['filingStatusStartingDate'],
     },
     NOT_ALIGNED_FILING_STATUSES_STARTING_ENDING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `The ending date for '{filingStatus}' must be after its starting date`,
+        message: `The ending date for {filingStatus} must be after its starting date`,
         params: ['filingStatus'],
         affectedFields: ['filingStatusStartingDate', 'filingStatusEndingDate'],
     },
     NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUSES_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Adjust the start date to be on or after the client's date established, '{clientStartDate}'.`,
+        message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
         params: ['clientStartDate'],
         affectedFields: ['filingStatusStartingDate', 'dateEstablished'],
     },
     NOT_ALIGNED_CLOSE_DATE_FILING_STATUSES_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Adjust the start date to be before the client's close date, '{clientCloseDate}'.`,
+        message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
         params: ['clientCloseDate'],
         affectedFields: ['filingStatusStartingDate', 'closeDate'],
     },
     FILING_STATUSES_DATE_GAP_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There is a gap in the timeframes between '{currentFilingStatus}', ending '{currentFilingStatusEndDate}', and '{nextFilingStatus}', starting '{nextFilingStatusStartDate}'. Please adjust the dates to fill this gap.`,
+        message: `There is a gap in the timeframes between {currentFilingStatus}, ending {currentFilingStatusEndDate}, and {nextFilingStatus}, starting {nextFilingStatusStartDate}. Please adjust the dates to fill this gap.`,
         params: ['currentFilingStatus', 'currentFilingStatusEndDate', 'nextFilingStatus', 'nextFilingStatusStartDate'],
         affectedFields: ['filingStatus'],
     },
     FILING_STATUSES_CONSECUTIVE_DUPLICATES_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There are two entries for '{filingStatus}' with timeframes that immediately follow each other. '{filingStatus}' ending '{firstPeriodEnd}', and '{filingStatus}' starting '{secondPeriodStart}'. Please update one entry to include the entire timeframe for '{filingStatus}'. `,
+        message: `There are two entries for {filingStatus} with timeframes that immediately follow each other. {filingStatus} ending {firstPeriodEnd}, and {filingStatus} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingStatus}. `,
         params: ['filingStatus', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
         affectedFields: ['filingStatus'],
     },
     FILING_STATUS_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There is a gap between the client's date established ('{dateEstablished}') and the start date of the first Sub/Parent status ('{earliestFilingStatusStartDate}'). Please ensure that the status of one Sub/Parent status matches the client's date established.`,
+        message: `There is a gap between the client's date established ({dateEstablished}) and the start date of the first Sub/Parent status ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.`,
         params: ['dateEstablished', 'earliestFilingStatusStartDate'],
         affectedFields: ['filingStatus', 'dateEstablished'],
     },
     FILING_STATUSES_DATES_OVERLAP: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `The client already has '{filingStatus}' starting from '{startDate2}' to '{endDate2}'. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
+        message: `The client already has {filingStatus} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
         params: ['filingStatus', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
         affectedFields: ['filingStatus'],
     },

package/dist/validation/features/client-records-outside-providers.validation-messages.js CHANGED Viewed

@@ -11,7 +11,7 @@ exports.CLIENT_RECORDS_OUTSIDE_PROVIDERS = (0, validation_message_types_1.define
     },
     SAME_TYPE_TIMELINE_OVERLAP: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `The client already has '{outsideProviderType}' starting from '{startDate}'. Your entry overlaps with that time. Please adjust the dates so they don't overlap.`,
+        message: `The client already has {outsideProviderType} starting from {startDate}. Your entry overlaps with that time. Please adjust the dates so they don't overlap.`,
         params: ['outsideProviderType', 'startDate'],
         affectedFields: ['starting', 'ending'],
     },

package/dist/validation/features/client-relationships-common.validation-messages.js CHANGED Viewed

@@ -10,79 +10,79 @@ exports.CLIENT_RELATIONSHIPS_COMMON = (0, validation_message_types_1.defineValid
     },
     INVALID_RELATIONSHIP_TYPE_FOR_ENTITY_TYPE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `'{clientName}' is a/an '{entityType}', which can't have '{relationshipType}'s. Please update the relationship type.`,
+        message: `{clientName} is a/an {entityType}, which can't have {relationshipType}s. Please update the relationship type.`,
         params: ['clientName', 'entityType', 'relationshipType'],
         affectedFields: ['relationshipType'],
     },
     STARTING_DATE_BEFORE_CLIENT_DATE_ESTABLISHED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `This relationship's start date cannot be before {clientName}'s date established, '{clientDateEstablished}'. Please adjust the dates to proceed.`,
+        message: `This relationship's start date cannot be before {clientName}'s date established, {clientDateEstablished}. Please adjust the dates to proceed.`,
         params: ['clientName', 'clientDateEstablished'],
         affectedFields: ['startingDate'],
     },
     STARTING_DATE_ON_OR_AFTER_CLIENT_CLOSE_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `This relationship's start date cannot be on or after {clientName}'s close date, '{clientCloseDate}'. Please adjust the dates to proceed.`,
+        message: `This relationship's start date cannot be on or after {clientName}'s close date, {clientCloseDate}. Please adjust the dates to proceed.`,
         params: ['clientName', 'clientCloseDate'],
         affectedFields: ['startingDate'],
     },
     STARTING_DATE_BEFORE_RELATED_CLIENT_DATE_ESTABLISHED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `This relationship's start date cannot be before {relatedClientName}'s date established, '{relatedClientDateEstablished}'. Please adjust the dates to proceed.`,
+        message: `This relationship's start date cannot be before {relatedClientName}'s date established, {relatedClientDateEstablished}. Please adjust the dates to proceed.`,
         params: ['relatedClientName', 'relatedClientDateEstablished'],
         affectedFields: ['startingDate'],
     },
     STARTING_DATE_ON_OR_AFTER_RELATED_CLIENT_CLOSE_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `This relationship's start date cannot be on or after {relatedClientName}'s close date, '{relatedClientCloseDate}'. Please adjust the dates to proceed.`,
+        message: `This relationship's start date cannot be on or after {relatedClientName}'s close date, {relatedClientCloseDate}. Please adjust the dates to proceed.`,
         params: ['relatedClientName', 'relatedClientCloseDate'],
         affectedFields: ['startingDate'],
     },
     ENDING_DATE_ON_OR_BEFORE_STARTING_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Please update the relationship ending date to be after the starting date, '{startingDate}'.`,
+        message: `Please update the relationship ending date to be after the starting date, {startingDate}.`,
         params: ['startingDate'],
         affectedFields: ['endingDate'],
     },
     ENDING_DATE_AFTER_CLIENT_CLOSE_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `{clientName}'s close date is '{clientCloseDate}'. One or more relationships have end dates later than this. Please update the following relationship end dates to be on or before '{clientCloseDate}': '{relationshipsWithEndingDateAfterCloseDate}', or update {clientName}'s close date.`,
+        message: `{clientName}'s close date is {clientCloseDate}. One or more relationships have end dates later than this. Please update the following relationship end dates to be on or before {clientCloseDate}: {relationshipsWithEndingDateAfterCloseDate}, or update {clientName}'s close date.`,
         params: ['clientName', 'clientCloseDate', 'relationshipsWithEndingDateAfterCloseDate'],
         affectedFields: ['endingDate'],
     },
     ENDING_DATE_AFTER_RELATED_CLIENT_CLOSE_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `{relatedClientName}'s close date is '{relatedClientCloseDate}'. One or more relationships have end dates later than this. Please update the following relationship end dates to be on or before '{relatedClientCloseDate}': '{relationshipsWithEndingDateAfterCloseDate}', or update {relatedClientName}'s close date.`,
+        message: `{relatedClientName}'s close date is {relatedClientCloseDate}. One or more relationships have end dates later than this. Please update the following relationship end dates to be on or before {relatedClientCloseDate}: {relationshipsWithEndingDateAfterCloseDate}, or update {relatedClientName}'s close date.`,
         params: ['relatedClientName', 'relatedClientCloseDate', 'relationshipsWithEndingDateAfterCloseDate'],
         affectedFields: ['endingDate'],
     },
     FINAL_REQUIRED_WHEN_ENDING_DATE_MATCHES_CLIENT_CLOSE_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `The relationship between '{clientName}' and '{relatedClientName}' has no end date or is not marked as final. Please update {relatedClientName}'s end date to be on or before {clientName}'s close date of '{clientCloseDate}', or mark the relationship as final.`,
+        message: `The relationship between {clientName} and {relatedClientName} has no end date or is not marked as final. Please update {relatedClientName}'s end date to be on or before {clientName}'s close date of {clientCloseDate}, or mark the relationship as final.`,
         params: ['clientName', 'relatedClientName', 'clientCloseDate'],
         affectedFields: ['endingDate', 'final'],
     },
     FINAL_REQUIRED_WHEN_ENDING_DATE_MATCHES_RELATED_CLIENT_CLOSE_DATE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `The relationship between '{clientName}' and '{relatedClientName}' has no end date or is not marked as final. Please update {clientName}'s end date to be on or before {relatedClientName}'s close date of '{relatedClientCloseDate}', or mark the relationship as final.`,
+        message: `The relationship between {clientName} and {relatedClientName} has no end date or is not marked as final. Please update {clientName}'s end date to be on or before {relatedClientName}'s close date of {relatedClientCloseDate}, or mark the relationship as final.`,
         params: ['clientName', 'relatedClientName', 'relatedClientCloseDate'],
         affectedFields: ['endingDate', 'final'],
     },
     CIRCULAR_RELATIONSHIP_DETECTED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `'{clientName}' is listed as a '{relationshipType}' of '{relatedClientName}', during the same timeframe that '{relatedClientName}' is listed as a '{relationshipType}' of '{clientName}'. Please review the relationship records for both clients and adjust the dates or relationship types to prevent a circular loop.`,
+        message: `{clientName} is listed as a {relationshipType} of {relatedClientName}, during the same timeframe that {relatedClientName} is listed as a {relationshipType} of {clientName}. Please review the relationship records for both clients and adjust the dates or relationship types to prevent a circular loop.`,
         params: ['clientName', 'relatedClientName', 'relationshipType'],
         affectedFields: ['relationshipType', 'relatedClient', 'startingDate', 'endingDate'],
     },
     CONFLICTING_RELATIONSHIP_TYPES_SAME_TIMEFRAME: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `'{relatedClientName}' cannot be associated with '{clientName}' more than once within the same timeframe. Please ensure there are no conflicting relationships for these clients in this timeframe.`,
+        message: `{relatedClientName} cannot be associated with {clientName} more than once within the same timeframe. Please ensure there are no conflicting relationships for these clients in this timeframe.`,
         params: ['relatedClientName', 'clientName'],
         affectedFields: ['relationshipType', 'relatedClient', 'startingDate', 'endingDate'],
     },
     CONSECUTIVE_DUPLICATE_RELATIONSHIPS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There is another '{relationshipType}' relationship between '{relatedClientName}' and '{clientName}' ending on '{relationshipEnding}'. Please review and adjust the dates to track this relationship in one record.`,
+        message: `There is another {relationshipType} relationship between {relatedClientName} and {clientName} ending on {relationshipEnding}. Please review and adjust the dates to track this relationship in one record.`,
         params: ['relationshipType', 'relatedClientName', 'clientName', 'relationshipEnding'],
         affectedFields: ['startingDate', 'endingDate'],
     },

package/dist/validation/features/client-relationships-income-sources.validation-messages.js CHANGED Viewed

@@ -5,7 +5,7 @@ const validation_message_types_1 = require("../validation-message.types");
 exports.CLIENT_RELATIONSHIPS_INCOME_SOURCES = (0, validation_message_types_1.defineValidationFeatureMessages)({
     SUBSIDIARY_CANNOT_HAVE_PARENT: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `'{clientName}' cannot have subsidiary relationships since it is filing as a subsidiary under '{parentClientName}' during this timeframe. Please adjust the timeframe or select a different relationship type.`,
+        message: `{clientName} cannot have subsidiary relationships since it is filing as a subsidiary under {parentClientName} during this timeframe. Please adjust the timeframe or select a different relationship type.`,
         params: ['clientName', 'parentClientName'],
         affectedFields: ['relationshipType', 'startingDate', 'endingDate'],
     },
@@ -66,7 +66,7 @@ exports.CLIENT_RELATIONSHIPS_INCOME_SOURCES = (0, validation_message_types_1.def
     },
     K1_ISSUER_INVALID_ENTITY_TYPE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `'{relatedClient}' is a/an '{entityType}', which cannot issue K1s. Please select a different client or choose a different relationship type.`,
+        message: `{relatedClient} is a/an {entityType}, which cannot issue K1s. Please select a different client or choose a different relationship type.`,
         params: ['relatedClient', 'entityType'],
         affectedFields: ['relatedClient', 'relationshipType'],
     },

package/dist/validation/features/client-relationships-owners.validation-messages.js CHANGED Viewed

@@ -15,13 +15,13 @@ exports.CLIENT_RELATIONSHIPS_OWNERS = (0, validation_message_types_1.defineValid
     },
     MULTIPLE_PARENT_RELATIONSHIPS_SAME_TIMEFRAME: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There can only be one parent relationship associated to a client during the same timeframe. There is a current parent relationship with '{parentRelatedClientName}' starting '{relationshipStarting}'. Please add an end date to that relationship before adding a new one.`,
+        message: `There can only be one parent relationship associated to a client during the same timeframe. There is a current parent relationship with {parentRelatedClientName} starting {relationshipStarting}. Please add an end date to that relationship before adding a new one.`,
         params: ['parentRelatedClientName', 'relationshipStarting'],
         affectedFields: ['relationshipType', 'startingDate'],
     },
     PARENT_CANNOT_BE_SUB_ENTITY: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `'{relatedClientName}' cannot be the parent of '{clientName}', since it is filing as a sub-entity under another parent during this timeframe. Please adjust the timeframe or select a different relationship type.`,
+        message: `{relatedClientName} cannot be the parent of {clientName}, since it is filing as a sub-entity under another parent during this timeframe. Please adjust the timeframe or select a different relationship type.`,
         params: ['relatedClientName', 'clientName'],
         affectedFields: ['relatedClient', 'relationshipType', 'startingDate', 'endingDate'],
     },

package/dist/validation/features/client-template-assignments.validation-messages.js CHANGED Viewed

@@ -25,7 +25,7 @@ exports.CLIENT_TEMPLATE_ASSIGNMENTS = (0, validation_message_types_1.defineValid
     },
     ORDER_NOT_CONSECUTIVE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: 'Assignment orders must be consecutive starting from 1. Expected orders: {expected}',
+        message: `Assignment orders must be consecutive starting from 1. Expected orders: {expected}`,
         params: ['expected'],
         affectedFields: ['assignments.order'],
     },

package/dist/validation/features/client-templates.validation-messages.d.ts.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"client-templates.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-templates.validation-messages.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,gBAAgB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;~~CAuL3B~~,CAAC"}
1	+ {"version":3,"file":"client-templates.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-templates.validation-messages.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,gBAAgB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0L3B,CAAC"}

package/dist/validation/features/client-templates.validation-messages.js CHANGED Viewed

@@ -165,7 +165,7 @@ exports.CLIENT_TEMPLATES = (0, validation_message_types_1.defineValidationFeatur
     },
     OVERRIDE_DAY_EXCEEDS_MONTH_MAX: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Day '{dayOfMonth}' is not valid for '{monthName}'. The maximum allowed day is '{maxDays}'.`,
+        message: `Day {dayOfMonth} is not valid for {monthName}. The maximum allowed day is {maxDays}.`,
         params: ['dayOfMonth', 'monthName', 'maxDays'],
         affectedFields: ['recurrence.dayOfMonth'],
     },

package/dist/validation/features/filing-categories.validation-messages.js CHANGED Viewed

@@ -16,7 +16,7 @@ exports.FILING_CATEGORIES = (0, validation_message_types_1.defineValidationFeatu
     },
     NAME_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Filing category with the same name '{name}' already exists`,
+        message: `Filing category with the same name {name} already exists`,
         params: ['name'],
         affectedFields: ['filingCategory'],
     },

package/dist/validation/features/income-accounts.validation-messages.js CHANGED Viewed

@@ -10,7 +10,7 @@ exports.INCOME_ACCOUNTS = (0, validation_message_types_1.defineValidationFeature
     },
     NAME_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: "Income account with the name '{name}' already exists",
+        message: 'Income account with the name {name} already exists',
         params: ['name'],
         affectedFields: ['name'],
     },

package/dist/validation/features/roles-and-permissions.validation-messages.js CHANGED Viewed

@@ -5,13 +5,13 @@ const validation_message_types_1 = require("../validation-message.types");
 exports.ROLES_AND_PERMISSIONS = (0, validation_message_types_1.defineValidationFeatureMessages)({
     ROLE_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Role with name '{name}' already exists`,
+        message: `Role with name {name} already exists`,
         params: ['name'],
         affectedFields: ['name'],
     },
     PERMISSION_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Permission with name '{name}' already exists`,
+        message: `Permission with name {name} already exists`,
         params: ['name'],
         affectedFields: ['name'],
     },
@@ -35,7 +35,7 @@ exports.ROLES_AND_PERMISSIONS = (0, validation_message_types_1.defineValidationF
     },
     ROLE_HAS_ASSIGNED_USERS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `Cannot delete role with name '{roleName}' because it has users assigned to it`,
+        message: `Cannot delete role with name {roleName} because it has users assigned to it`,
         params: ['roleName'],
         affectedFields: [],
     },

package/dist/validation/features/states.validation-messages.js CHANGED Viewed

@@ -16,7 +16,7 @@ exports.STATES = (0, validation_message_types_1.defineValidationFeatureMessages)
     },
     NAME_ALREADY_EXISTS: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `State with the same name '{name}' already exists`,
+        message: `State with the same name {name} already exists`,
         params: ['name'],
         affectedFields: ['name'],
     },
@@ -44,13 +44,13 @@ exports.STATES = (0, validation_message_types_1.defineValidationFeatureMessages)
     },
     STATE_PARENT_TYPE_NOT_ALLOWED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There must be a nation associated with the state '{stateName}'. Please select a nation to proceed.`,
+        message: `There must be a nation associated with the state {stateName}. Please select a nation to proceed.`,
         params: ['stateName'],
         affectedFields: ['parent'],
     },
     CITY_PARENT_TYPE_NOT_ALLOWED: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: `There must be a state associated with the city '{cityName}'. Please select a state to proceed.`,
+        message: `There must be a state associated with the city {cityName}. Please select a state to proceed.`,
         params: ['cityName'],
         affectedFields: ['parent'],
     },

package/dist/validation/features/template-assignments.validation-messages.js CHANGED Viewed

@@ -85,7 +85,7 @@ exports.TEMPLATE_ASSIGNMENTS = (0, validation_message_types_1.defineValidationFe
     },
     ASSIGNMENTS_ORDER_NOT_CONSECUTIVE: {
         severity: validation_message_types_1.VALIDATION_SEVERITY.ERROR,
-        message: 'Assignment orders must be consecutive starting from 1. Expected orders: {expected}',
+        message: `Assignment orders must be consecutive starting from 1. Expected orders: {expected}`,
         params: ['expected'],
         affectedFields: ['assignments'],
     },

package/dist/validation/features/template-information.validation-messages.d.ts CHANGED Viewed

@@ -206,6 +206,12 @@ export declare const TEMPLATE_INFORMATION: {
         params: string[];
         affectedFields: string[];
     };
+    PARENT_FILING_CANNOT_FILE_UNDER_PARENT: {
+        severity: "error";
+        message: string;
+        params: string[];
+        affectedFields: string[];
+    };
     TAX_PAYMENT_FILING_REQUIRED: {
         severity: "error";
         message: string;

package/dist/validation/features/template-information.validation-messages.d.ts.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"template-information.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/template-information.validation-messages.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,oBAAoB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqV/B,CAAC"}
1	+ {"version":3,"file":"template-information.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/template-information.validation-messages.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,oBAAoB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6U/B,CAAC"}