@forwardslashns/taskit-validation-messages 1.0.29 → 1.0.31

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 (4) hide show
  1. package/dist/validation/validation-messages.d.ts +13 -13
  2. package/dist/validation/validation-messages.js +13 -13
  3. package/package.json +1 -1
  4. package/src/validation/validation-messages.ts +13 -13
package/dist/validation/validation-messages.d.ts CHANGED
@@ -68,7 +68,7 @@ export declare const VALIDATION_MESSAGES: {
68
68
  readonly params: readonly ["id"];
69
69
  };
70
70
  readonly FILING_TYPE_ID_DOES_NOT_EXIST: {
71
- readonly message: "Filing type with id '{id}' does not exist";
71
+ readonly message: "Parent/Sub status with id '{id}' does not exist";
72
72
  readonly params: readonly ["id"];
73
73
  };
74
74
  readonly STATE_ID_DOES_NOT_EXIST: {
@@ -106,7 +106,7 @@ export declare const VALIDATION_MESSAGES: {
106
106
  readonly params: readonly ["clientDateEstablished", "entityType", "entityTypeStartingDate"];
107
107
  };
108
108
  readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
109
- readonly message: "The filing type status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the filing type status or the client's date established.";
109
+ readonly 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.";
110
110
  readonly params: readonly ["clientDateEstablished", "filingType", "filingTypeStartingDate"];
111
111
  };
112
112
  readonly NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
@@ -121,14 +121,14 @@ export declare const VALIDATION_MESSAGES: {
121
121
  readonly params: readonly ["clientCloseDate", "entityType", "entityTypeStartingDate"];
122
122
  };
123
123
  readonly NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
124
- readonly message: "One or more filing type statuses 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.";
124
+ readonly 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.";
125
125
  readonly params: readonly ["clientCloseDate", "filingType", "filingTypeStartingDate"];
126
126
  };
127
127
  readonly ENTITY_TYPE_STARTING_DATE_NOT_POPULATED: {
128
128
  readonly message: "Current Entity Type Starting Date cannot be Empty";
129
129
  };
130
130
  readonly FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
131
- readonly message: "Current Filing Type Starting Date cannot be Empty";
131
+ readonly message: "Current Parent/Sub status Starting Date cannot be Empty";
132
132
  };
133
133
  readonly DOMESTIC_STATE_STARTING_DATE_NOT_POPULATED: {
134
134
  readonly message: "Current Domestic State Starting Date cannot be Empty";
@@ -137,7 +137,7 @@ export declare const VALIDATION_MESSAGES: {
137
137
  readonly message: "Entity type starting date needs to be before the ending date";
138
138
  };
139
139
  readonly NOT_ALIGNED_FILING_TYPE_STARTING_ENDING_DATE: {
140
- readonly message: "Filing type starting date needs to be before the ending date";
140
+ readonly message: "Parent/Sub status starting date needs to be before the ending date";
141
141
  };
142
142
  readonly NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
143
143
  readonly 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.";
@@ -247,17 +247,17 @@ export declare const VALIDATION_MESSAGES: {
247
247
  readonly message: "The current entity type cannot have an end date. Please remove the end date for this state.";
248
248
  };
249
249
  readonly FILING_TYPES_IDS_DOES_NOT_EXIST: {
250
- readonly message: "Filing types with ids '{ids}' do not exist";
250
+ readonly message: "Parent/Sub status with ids '{ids}' do not exist";
251
251
  readonly params: readonly ["ids"];
252
252
  };
253
253
  readonly AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
254
- readonly message: "At least one filing type should exist";
254
+ readonly message: "At least one Parent/Sub status should exist";
255
255
  };
256
256
  readonly FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
257
- readonly message: "Filing Type Starting Date cannot be Empty";
257
+ readonly message: "Parent/Sub status Starting Date cannot be Empty";
258
258
  };
259
259
  readonly NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
260
- readonly message: "Filing type starting date needs to be before the ending date";
260
+ readonly message: "Parent/Sub status starting date needs to be before the ending date";
261
261
  };
262
262
  readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
263
263
  readonly message: "Adjust the start date to be on or after the client's date established, {clientStartDate}.";
@@ -276,18 +276,18 @@ export declare const VALIDATION_MESSAGES: {
276
276
  readonly params: readonly ["filingType", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
277
277
  };
278
278
  readonly FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
279
- readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of its first filing type ({earliestFilingType} starting {earliestFilingTypeStartDate}). There must be a filing type that begins on {dateEstablished}.";
279
+ readonly 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}.";
280
280
  readonly params: readonly ["dateEstablished", "earliestFilingType", "earliestFilingTypeStartDate"];
281
281
  };
282
282
  readonly FILING_TYPES_DATES_OVERLAP: {
283
- readonly message: "There are multiple entries for {filingType} with overlapping timeframes: {filingType} from {startDate1} to {endDate1}, {filingType} from {startDate2} to {endDate2}. A filing type cannot appear more than once with overlapping dates. Please adjust the dates on the new or existing {filingType} entries to remove the overlap.";
283
+ readonly message: "There are multiple entries for {filingType} with overlapping timeframes: {filingType} from {startDate1} to {endDate1}, {filingType} from {startDate2} to {endDate2}. A Parent/Sub status cannot appear more than once with overlapping dates. Please adjust the dates on the new or existing {filingType} entries to remove the overlap.";
284
284
  readonly params: readonly ["filingType", "startDate1", "endDate1", "startDate2", "endDate2"];
285
285
  };
286
286
  readonly ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
287
- readonly message: "Only the last filing type can be open without an end date. Add an ending date to the existing filing type before adding a start date for a new filing type.";
287
+ readonly 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.";
288
288
  };
289
289
  readonly CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
290
- readonly message: "The current filing type cannot have an end date. Please remove the end date for this state.";
290
+ readonly message: "The current Parent/Sub status cannot have an end date. Please remove the end date for this state.";
291
291
  };
292
292
  readonly STATES_IDS_DOES_NOT_EXIST: {
293
293
  readonly message: "States with ids '{ids}' do not exist";
package/dist/validation/validation-messages.js CHANGED
@@ -71,7 +71,7 @@ exports.VALIDATION_MESSAGES = {
71
71
  params: ['id'],
72
72
  },
73
73
  FILING_TYPE_ID_DOES_NOT_EXIST: {
74
- message: `Filing type with id '{id}' does not exist`,
74
+ message: `Parent/Sub status with id '{id}' does not exist`,
75
75
  params: ['id'],
76
76
  },
77
77
  STATE_ID_DOES_NOT_EXIST: {
@@ -109,7 +109,7 @@ exports.VALIDATION_MESSAGES = {
109
109
  params: ['clientDateEstablished', 'entityType', 'entityTypeStartingDate'],
110
110
  },
111
111
  NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
112
- message: `The filing type status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the filing type status or the client's date established.`,
112
+ 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.`,
113
113
  params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
114
114
  },
115
115
  NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
@@ -124,14 +124,14 @@ exports.VALIDATION_MESSAGES = {
124
124
  params: ['clientCloseDate', 'entityType', 'entityTypeStartingDate'],
125
125
  },
126
126
  NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
127
- message: `One or more filing type statuses 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.`,
127
+ 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.`,
128
128
  params: ['clientCloseDate', 'filingType', 'filingTypeStartingDate'],
129
129
  },
130
130
  ENTITY_TYPE_STARTING_DATE_NOT_POPULATED: {
131
131
  message: `Current Entity Type Starting Date cannot be Empty`,
132
132
  },
133
133
  FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
134
- message: `Current Filing Type Starting Date cannot be Empty`,
134
+ message: `Current Parent/Sub status Starting Date cannot be Empty`,
135
135
  },
136
136
  DOMESTIC_STATE_STARTING_DATE_NOT_POPULATED: {
137
137
  message: `Current Domestic State Starting Date cannot be Empty`,
@@ -140,7 +140,7 @@ exports.VALIDATION_MESSAGES = {
140
140
  message: `Entity type starting date needs to be before the ending date`,
141
141
  },
142
142
  NOT_ALIGNED_FILING_TYPE_STARTING_ENDING_DATE: {
143
- message: `Filing type starting date needs to be before the ending date`,
143
+ message: `Parent/Sub status starting date needs to be before the ending date`,
144
144
  },
145
145
  NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
146
146
  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.`,
@@ -252,17 +252,17 @@ exports.VALIDATION_MESSAGES = {
252
252
  },
253
253
  //UPDATE-FILING-TYPES-VALIDATIONS
254
254
  FILING_TYPES_IDS_DOES_NOT_EXIST: {
255
- message: `Filing types with ids '{ids}' do not exist`,
255
+ message: `Parent/Sub status with ids '{ids}' do not exist`,
256
256
  params: ['ids'],
257
257
  },
258
258
  AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
259
- message: `At least one filing type should exist`,
259
+ message: `At least one Parent/Sub status should exist`,
260
260
  },
261
261
  FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
262
- message: `Filing Type Starting Date cannot be Empty`,
262
+ message: `Parent/Sub status Starting Date cannot be Empty`,
263
263
  },
264
264
  NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
265
- message: `Filing type starting date needs to be before the ending date`,
265
+ message: `Parent/Sub status starting date needs to be before the ending date`,
266
266
  },
267
267
  NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
268
268
  message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
@@ -281,18 +281,18 @@ exports.VALIDATION_MESSAGES = {
281
281
  params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
282
282
  },
283
283
  FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
284
- message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first filing type ({earliestFilingType} starting {earliestFilingTypeStartDate}). There must be a filing type that begins on {dateEstablished}.`,
284
+ 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}.`,
285
285
  params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
286
286
  },
287
287
  FILING_TYPES_DATES_OVERLAP: {
288
- message: `There are multiple entries for {filingType} with overlapping timeframes: {filingType} from {startDate1} to {endDate1}, {filingType} from {startDate2} to {endDate2}. A filing type cannot appear more than once with overlapping dates. Please adjust the dates on the new or existing {filingType} entries to remove the overlap.`,
288
+ message: `There are multiple entries for {filingType} with overlapping timeframes: {filingType} from {startDate1} to {endDate1}, {filingType} from {startDate2} to {endDate2}. A Parent/Sub status cannot appear more than once with overlapping dates. Please adjust the dates on the new or existing {filingType} entries to remove the overlap.`,
289
289
  params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
290
290
  },
291
291
  ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
292
- message: `Only the last filing type can be open without an end date. Add an ending date to the existing filing type before adding a start date for a new filing type.`,
292
+ 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.`,
293
293
  },
294
294
  CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
295
- message: `The current filing type cannot have an end date. Please remove the end date for this state.`,
295
+ message: `The current Parent/Sub status cannot have an end date. Please remove the end date for this state.`,
296
296
  },
297
297
  //UPDATE-STATES-VALIDATIONS
298
298
  STATES_IDS_DOES_NOT_EXIST: {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@forwardslashns/taskit-validation-messages",
3
- "version": "1.0.29",
3
+ "version": "1.0.31",
4
4
  "main": "dist/index.js",
5
5
  "types": "dist/index.d.ts",
6
6
  "type": "commonjs",
package/src/validation/validation-messages.ts CHANGED
@@ -68,7 +68,7 @@ export const VALIDATION_MESSAGES = {
68
68
  params: ['id'],
69
69
  },
70
70
  FILING_TYPE_ID_DOES_NOT_EXIST: {
71
- message: `Filing type with id '{id}' does not exist`,
71
+ message: `Parent/Sub status with id '{id}' does not exist`,
72
72
  params: ['id'],
73
73
  },
74
74
  STATE_ID_DOES_NOT_EXIST: {
@@ -106,7 +106,7 @@ export const VALIDATION_MESSAGES = {
106
106
  params: ['clientDateEstablished', 'entityType', 'entityTypeStartingDate'],
107
107
  },
108
108
  NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
109
- message: `The filing type status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the filing type status or the client's date established.`,
109
+ 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.`,
110
110
  params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
111
111
  },
112
112
  NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
@@ -121,14 +121,14 @@ export const VALIDATION_MESSAGES = {
121
121
  params: ['clientCloseDate', 'entityType', 'entityTypeStartingDate'],
122
122
  },
123
123
  NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
124
- message: `One or more filing type statuses 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.`,
124
+ 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.`,
125
125
  params: ['clientCloseDate', 'filingType', 'filingTypeStartingDate'],
126
126
  },
127
127
  ENTITY_TYPE_STARTING_DATE_NOT_POPULATED: {
128
128
  message: `Current Entity Type Starting Date cannot be Empty`,
129
129
  },
130
130
  FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
131
- message: `Current Filing Type Starting Date cannot be Empty`,
131
+ message: `Current Parent/Sub status Starting Date cannot be Empty`,
132
132
  },
133
133
  DOMESTIC_STATE_STARTING_DATE_NOT_POPULATED: {
134
134
  message: `Current Domestic State Starting Date cannot be Empty`,
@@ -137,7 +137,7 @@ export const VALIDATION_MESSAGES = {
137
137
  message: `Entity type starting date needs to be before the ending date`,
138
138
  },
139
139
  NOT_ALIGNED_FILING_TYPE_STARTING_ENDING_DATE: {
140
- message: `Filing type starting date needs to be before the ending date`,
140
+ message: `Parent/Sub status starting date needs to be before the ending date`,
141
141
  },
142
142
  NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
143
143
  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.`,
@@ -249,17 +249,17 @@ export const VALIDATION_MESSAGES = {
249
249
  },
250
250
  //UPDATE-FILING-TYPES-VALIDATIONS
251
251
  FILING_TYPES_IDS_DOES_NOT_EXIST: {
252
- message: `Filing types with ids '{ids}' do not exist`,
252
+ message: `Parent/Sub status with ids '{ids}' do not exist`,
253
253
  params: ['ids'],
254
254
  },
255
255
  AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
256
- message: `At least one filing type should exist`,
256
+ message: `At least one Parent/Sub status should exist`,
257
257
  },
258
258
  FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
259
- message: `Filing Type Starting Date cannot be Empty`,
259
+ message: `Parent/Sub status Starting Date cannot be Empty`,
260
260
  },
261
261
  NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
262
- message: `Filing type starting date needs to be before the ending date`,
262
+ message: `Parent/Sub status starting date needs to be before the ending date`,
263
263
  },
264
264
  NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
265
265
  message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
@@ -278,18 +278,18 @@ export const VALIDATION_MESSAGES = {
278
278
  params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
279
279
  },
280
280
  FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
281
- message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first filing type ({earliestFilingType} starting {earliestFilingTypeStartDate}). There must be a filing type that begins on {dateEstablished}.`,
281
+ 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}.`,
282
282
  params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
283
283
  },
284
284
  FILING_TYPES_DATES_OVERLAP: {
285
- message: `There are multiple entries for {filingType} with overlapping timeframes: {filingType} from {startDate1} to {endDate1}, {filingType} from {startDate2} to {endDate2}. A filing type cannot appear more than once with overlapping dates. Please adjust the dates on the new or existing {filingType} entries to remove the overlap.`,
285
+ message: `There are multiple entries for {filingType} with overlapping timeframes: {filingType} from {startDate1} to {endDate1}, {filingType} from {startDate2} to {endDate2}. A Parent/Sub status cannot appear more than once with overlapping dates. Please adjust the dates on the new or existing {filingType} entries to remove the overlap.`,
286
286
  params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
287
287
  },
288
288
  ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
289
- message: `Only the last filing type can be open without an end date. Add an ending date to the existing filing type before adding a start date for a new filing type.`,
289
+ 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.`,
290
290
  },
291
291
  CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
292
- message: `The current filing type cannot have an end date. Please remove the end date for this state.`,
292
+ message: `The current Parent/Sub status cannot have an end date. Please remove the end date for this state.`,
293
293
  },
294
294
  //UPDATE-STATES-VALIDATIONS
295
295
  STATES_IDS_DOES_NOT_EXIST: {