@forwardslashns/taskit-validation-messages 1.0.7 → 1.0.9
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.
|
@@ -110,8 +110,8 @@ export declare const VALIDATION_MESSAGES: {
|
|
|
110
110
|
readonly params: readonly ["clientDateEstablished", "filingType", "filingTypeStartingDate"];
|
|
111
111
|
};
|
|
112
112
|
readonly NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
|
|
113
|
-
readonly message: "
|
|
114
|
-
readonly params: readonly ["
|
|
113
|
+
readonly message: "Adjust the start date to be on or after the client's date established, {domesticStateStartingDate}.";
|
|
114
|
+
readonly params: readonly ["domesticStateStartingDate"];
|
|
115
115
|
};
|
|
116
116
|
readonly NOT_ALIGNED_DATE_ESTABLISHED_CLOSE_DATE: {
|
|
117
117
|
readonly message: "Adjust the close date to be after the date established.";
|
|
@@ -218,6 +218,10 @@ export declare const VALIDATION_MESSAGES: {
|
|
|
218
218
|
readonly 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}.";
|
|
219
219
|
readonly params: readonly ["dateEstablished", "earliestState", "earliestStateStartDate"];
|
|
220
220
|
};
|
|
221
|
+
readonly DOMESTIC_STATE_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
222
|
+
readonly 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}. ";
|
|
223
|
+
readonly params: readonly ["state", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
|
|
224
|
+
};
|
|
221
225
|
};
|
|
222
226
|
readonly FILING_CATEGORY: {
|
|
223
227
|
readonly INVALID_REQUEST: {
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"validation-messages.d.ts","sourceRoot":"","sources":["../../src/validation/validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,mBAAmB
|
|
1
|
+
{"version":3,"file":"validation-messages.d.ts","sourceRoot":"","sources":["../../src/validation/validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,mBAAmB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoUtB,CAAC"}
|
|
@@ -113,10 +113,8 @@ exports.VALIDATION_MESSAGES = {
|
|
|
113
113
|
params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
|
|
114
114
|
},
|
|
115
115
|
NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
|
|
116
|
-
message: `
|
|
116
|
+
message: `Adjust the start date to be on or after the client's date established, {domesticStateStartingDate}.`,
|
|
117
117
|
params: [
|
|
118
|
-
'clientDateEstablished',
|
|
119
|
-
'domesticState',
|
|
120
118
|
'domesticStateStartingDate',
|
|
121
119
|
],
|
|
122
120
|
},
|
|
@@ -225,6 +223,10 @@ exports.VALIDATION_MESSAGES = {
|
|
|
225
223
|
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}.`,
|
|
226
224
|
params: ['dateEstablished', 'earliestState', 'earliestStateStartDate'],
|
|
227
225
|
},
|
|
226
|
+
DOMESTIC_STATE_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
227
|
+
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}. `,
|
|
228
|
+
params: ['state', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
|
|
229
|
+
},
|
|
228
230
|
},
|
|
229
231
|
FILING_CATEGORY: {
|
|
230
232
|
INVALID_REQUEST: {
|
package/package.json
CHANGED
|
@@ -110,10 +110,8 @@ export const VALIDATION_MESSAGES = {
|
|
|
110
110
|
params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
|
|
111
111
|
},
|
|
112
112
|
NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
|
|
113
|
-
message: `
|
|
113
|
+
message: `Adjust the start date to be on or after the client's date established, {domesticStateStartingDate}.`,
|
|
114
114
|
params: [
|
|
115
|
-
'clientDateEstablished',
|
|
116
|
-
'domesticState',
|
|
117
115
|
'domesticStateStartingDate',
|
|
118
116
|
],
|
|
119
117
|
},
|
|
@@ -222,6 +220,10 @@ export const VALIDATION_MESSAGES = {
|
|
|
222
220
|
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}.`,
|
|
223
221
|
params: ['dateEstablished', 'earliestState', 'earliestStateStartDate'],
|
|
224
222
|
},
|
|
223
|
+
DOMESTIC_STATE_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
224
|
+
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}. `,
|
|
225
|
+
params: ['state', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
|
|
226
|
+
},
|
|
225
227
|
},
|
|
226
228
|
FILING_CATEGORY: {
|
|
227
229
|
INVALID_REQUEST: {
|