@forwardslashns/taskit-validation-messages 1.0.28 → 1.0.30

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 (5) hide show
  1. package/dist/validation/validation-messages.d.ts +21 -12
  2. package/dist/validation/validation-messages.d.ts.map +1 -1
  3. package/dist/validation/validation-messages.js +21 -12
  4. package/package.json +1 -1
  5. package/src/validation/validation-messages.ts +21 -12
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 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 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 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.";
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.";
@@ -243,18 +243,21 @@ export declare const VALIDATION_MESSAGES: {
243
243
  readonly ALL_NON_LAST_ENTITY_TYPES_REQUIRE_ENDING_DATE: {
244
244
  readonly 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.";
245
245
  };
246
+ readonly CURRENT_ENTITY_TYPE_CANNOT_HAVE_ENDING_DATE: {
247
+ readonly message: "The current entity type cannot have an end date. Please remove the end date for this state.";
248
+ };
246
249
  readonly FILING_TYPES_IDS_DOES_NOT_EXIST: {
247
- readonly message: "Filing types with ids '{ids}' do not exist";
250
+ readonly message: "Parent/Sub statuss with ids '{ids}' do not exist";
248
251
  readonly params: readonly ["ids"];
249
252
  };
250
253
  readonly AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
251
- readonly message: "At least one filing type should exist";
254
+ readonly message: "At least one Parent/Sub status should exist";
252
255
  };
253
256
  readonly FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
254
- readonly message: "Filing Type Starting Date cannot be Empty";
257
+ readonly message: "Parent/Sub status Starting Date cannot be Empty";
255
258
  };
256
259
  readonly NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
257
- 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";
258
261
  };
259
262
  readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
260
263
  readonly message: "Adjust the start date to be on or after the client's date established, {clientStartDate}.";
@@ -273,15 +276,18 @@ export declare const VALIDATION_MESSAGES: {
273
276
  readonly params: readonly ["filingType", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
274
277
  };
275
278
  readonly FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
276
- 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}.";
277
280
  readonly params: readonly ["dateEstablished", "earliestFilingType", "earliestFilingTypeStartDate"];
278
281
  };
279
282
  readonly FILING_TYPES_DATES_OVERLAP: {
280
- 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.";
281
284
  readonly params: readonly ["filingType", "startDate1", "endDate1", "startDate2", "endDate2"];
282
285
  };
283
286
  readonly ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
284
- 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
+ };
289
+ readonly CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
290
+ readonly message: "The current Parent/Sub status cannot have an end date. Please remove the end date for this state.";
285
291
  };
286
292
  readonly STATES_IDS_DOES_NOT_EXIST: {
287
293
  readonly message: "States with ids '{ids}' do not exist";
@@ -323,6 +329,9 @@ export declare const VALIDATION_MESSAGES: {
323
329
  readonly ALL_NON_LAST_DOMESTIC_STATES_REQUIRE_ENDING_DATE: {
324
330
  readonly 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.";
325
331
  };
332
+ readonly CURRENT_DOMESTIC_STATE_CANNOT_HAVE_ENDING_DATE: {
333
+ readonly message: "The current domestic state cannot have an end date. Please remove the end date for this state.";
334
+ };
326
335
  };
327
336
  readonly FILING_CATEGORY: {
328
337
  readonly INVALID_REQUEST: {
package/dist/validation/validation-messages.d.ts.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"validation-messages.d.ts","sourceRoot":"","sources":["../../src/validation/validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,mBAAmB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyatB,CAAC"}
1
+ {"version":3,"file":"validation-messages.d.ts","sourceRoot":"","sources":["../../src/validation/validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,mBAAmB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkbtB,CAAC"}
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 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 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 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.`,
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.`,
@@ -247,19 +247,22 @@ exports.VALIDATION_MESSAGES = {
247
247
  ALL_NON_LAST_ENTITY_TYPES_REQUIRE_ENDING_DATE: {
248
248
  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.`,
249
249
  },
250
+ CURRENT_ENTITY_TYPE_CANNOT_HAVE_ENDING_DATE: {
251
+ message: `The current entity type cannot have an end date. Please remove the end date for this state.`,
252
+ },
250
253
  //UPDATE-FILING-TYPES-VALIDATIONS
251
254
  FILING_TYPES_IDS_DOES_NOT_EXIST: {
252
- message: `Filing types with ids '{ids}' do not exist`,
255
+ message: `Parent/Sub statuss with ids '{ids}' do not exist`,
253
256
  params: ['ids'],
254
257
  },
255
258
  AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
256
- message: `At least one filing type should exist`,
259
+ message: `At least one Parent/Sub status should exist`,
257
260
  },
258
261
  FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
259
- message: `Filing Type Starting Date cannot be Empty`,
262
+ message: `Parent/Sub status Starting Date cannot be Empty`,
260
263
  },
261
264
  NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
262
- 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`,
263
266
  },
264
267
  NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
265
268
  message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
@@ -278,15 +281,18 @@ exports.VALIDATION_MESSAGES = {
278
281
  params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
279
282
  },
280
283
  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}.`,
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}.`,
282
285
  params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
283
286
  },
284
287
  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.`,
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.`,
286
289
  params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
287
290
  },
288
291
  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.`,
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
+ },
294
+ CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
295
+ message: `The current Parent/Sub status cannot have an end date. Please remove the end date for this state.`,
290
296
  },
291
297
  //UPDATE-STATES-VALIDATIONS
292
298
  STATES_IDS_DOES_NOT_EXIST: {
@@ -329,6 +335,9 @@ exports.VALIDATION_MESSAGES = {
329
335
  ALL_NON_LAST_DOMESTIC_STATES_REQUIRE_ENDING_DATE: {
330
336
  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.`,
331
337
  },
338
+ CURRENT_DOMESTIC_STATE_CANNOT_HAVE_ENDING_DATE: {
339
+ message: `The current domestic state cannot have an end date. Please remove the end date for this state.`,
340
+ },
332
341
  },
333
342
  FILING_CATEGORY: {
334
343
  INVALID_REQUEST: {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@forwardslashns/taskit-validation-messages",
3
- "version": "1.0.28",
3
+ "version": "1.0.30",
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 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 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 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.`,
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.`,
@@ -244,19 +244,22 @@ export const VALIDATION_MESSAGES = {
244
244
  ALL_NON_LAST_ENTITY_TYPES_REQUIRE_ENDING_DATE: {
245
245
  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.`,
246
246
  },
247
+ CURRENT_ENTITY_TYPE_CANNOT_HAVE_ENDING_DATE: {
248
+ message: `The current entity type cannot have an end date. Please remove the end date for this state.`,
249
+ },
247
250
  //UPDATE-FILING-TYPES-VALIDATIONS
248
251
  FILING_TYPES_IDS_DOES_NOT_EXIST: {
249
- message: `Filing types with ids '{ids}' do not exist`,
252
+ message: `Parent/Sub statuss with ids '{ids}' do not exist`,
250
253
  params: ['ids'],
251
254
  },
252
255
  AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
253
- message: `At least one filing type should exist`,
256
+ message: `At least one Parent/Sub status should exist`,
254
257
  },
255
258
  FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
256
- message: `Filing Type Starting Date cannot be Empty`,
259
+ message: `Parent/Sub status Starting Date cannot be Empty`,
257
260
  },
258
261
  NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
259
- 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`,
260
263
  },
261
264
  NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
262
265
  message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
@@ -275,15 +278,18 @@ export const VALIDATION_MESSAGES = {
275
278
  params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
276
279
  },
277
280
  FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
278
- 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}.`,
279
282
  params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
280
283
  },
281
284
  FILING_TYPES_DATES_OVERLAP: {
282
- 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.`,
283
286
  params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
284
287
  },
285
288
  ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
286
- 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
+ },
291
+ CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
292
+ message: `The current Parent/Sub status cannot have an end date. Please remove the end date for this state.`,
287
293
  },
288
294
  //UPDATE-STATES-VALIDATIONS
289
295
  STATES_IDS_DOES_NOT_EXIST: {
@@ -326,6 +332,9 @@ export const VALIDATION_MESSAGES = {
326
332
  ALL_NON_LAST_DOMESTIC_STATES_REQUIRE_ENDING_DATE: {
327
333
  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.`,
328
334
  },
335
+ CURRENT_DOMESTIC_STATE_CANNOT_HAVE_ENDING_DATE: {
336
+ message: `The current domestic state cannot have an end date. Please remove the end date for this state.`,
337
+ },
329
338
  },
330
339
  FILING_CATEGORY: {
331
340
  INVALID_REQUEST: {