@forwardslashns/taskit-validation-messages 1.3.3 → 1.3.5

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.
@@ -59,5 +59,43 @@ export declare const CLIENT_RELATIONSHIPS: {
59
59
  readonly message: "The related client has a close date that is the same as the relationship ending date, therefore the relationship must be marked as final. Please update the relationship's final status to 'Yes', or adjust the dates.";
60
60
  readonly affectedFields: readonly ["isFinal"];
61
61
  };
62
+ readonly CIRCULAR_RELATIONSHIP_DETECTED: {
63
+ readonly 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.";
64
+ readonly params: readonly ["clientName", "relatedClientName", "relationshipType"];
65
+ readonly affectedFields: readonly ["relationshipTypeId", "relatedClientId", "startingDate", "endingDate"];
66
+ };
67
+ readonly CONFLICTING_RELATIONSHIP_TYPES_SAME_TIMEFRAME: {
68
+ readonly 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.";
69
+ readonly params: readonly ["relatedClientName", "clientName"];
70
+ readonly affectedFields: readonly ["relationshipTypeId", "relatedClientId", "startingDate", "endingDate"];
71
+ };
72
+ readonly MULTIPLE_PARENT_RELATIONSHIPS_SAME_TIMEFRAME: {
73
+ readonly 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.";
74
+ readonly params: readonly ["parentRelatedClientName", "relationshipStarting"];
75
+ readonly affectedFields: readonly ["relationshipTypeId", "startingDate"];
76
+ };
77
+ readonly PARENT_CANNOT_BE_SUB_ENTITY: {
78
+ readonly 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.";
79
+ readonly params: readonly ["relatedClientName", "clientName"];
80
+ readonly affectedFields: readonly ["relatedClientId", "relationshipTypeId", "startingDate", "endingDate"];
81
+ };
82
+ readonly PARENT_ENTITY_TYPE_MISMATCH: {
83
+ readonly message: "A parent entity must be the same entity type as the client during the relationship's timeframe. Please select a different relationship type or update either client's entity type.";
84
+ readonly affectedFields: readonly ["relatedClientId", "relationshipTypeId"];
85
+ };
86
+ readonly CONSECUTIVE_DUPLICATE_RELATIONSHIPS: {
87
+ readonly 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.";
88
+ readonly params: readonly ["relationshipType", "relatedClientName", "clientName", "relationshipEnding"];
89
+ readonly affectedFields: readonly ["startingDate", "endingDate"];
90
+ };
91
+ readonly SUBSIDIARY_CANNOT_HAVE_PARENT: {
92
+ readonly 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.";
93
+ readonly params: readonly ["clientName", "parentClientName"];
94
+ readonly affectedFields: readonly ["relationshipTypeId", "startingDate", "endingDate"];
95
+ };
96
+ readonly SUBSIDIARY_REQUIRES_FILES_SEPARATELY: {
97
+ readonly message: "A subsidiary relationship can only be added to an entity that files separately. Please update the Sub/Parent status before adding a subsidiary relationship, or choose a different relationship type.";
98
+ readonly affectedFields: readonly ["relationshipTypeId", "filingTypeId"];
99
+ };
62
100
  };
63
101
  //# sourceMappingURL=client-relationships.validation-messages.d.ts.map
@@ -1 +1 @@
1
- {"version":3,"file":"client-relationships.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-relationships.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,oBAAoB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6DvB,CAAC"}
1
+ {"version":3,"file":"client-relationships.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-relationships.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,oBAAoB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmGvB,CAAC"}
@@ -62,4 +62,42 @@ exports.CLIENT_RELATIONSHIPS = {
62
62
  message: `The related client has a close date that is the same as the relationship ending date, therefore the relationship must be marked as final. Please update the relationship's final status to 'Yes', or adjust the dates.`,
63
63
  affectedFields: ['isFinal'],
64
64
  },
65
+ CIRCULAR_RELATIONSHIP_DETECTED: {
66
+ 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.`,
67
+ params: ['clientName', 'relatedClientName', 'relationshipType'],
68
+ affectedFields: ['relationshipTypeId', 'relatedClientId', 'startingDate', 'endingDate'],
69
+ },
70
+ CONFLICTING_RELATIONSHIP_TYPES_SAME_TIMEFRAME: {
71
+ 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.`,
72
+ params: ['relatedClientName', 'clientName'],
73
+ affectedFields: ['relationshipTypeId', 'relatedClientId', 'startingDate', 'endingDate'],
74
+ },
75
+ MULTIPLE_PARENT_RELATIONSHIPS_SAME_TIMEFRAME: {
76
+ 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.`,
77
+ params: ['parentRelatedClientName', 'relationshipStarting'],
78
+ affectedFields: ['relationshipTypeId', 'startingDate'],
79
+ },
80
+ PARENT_CANNOT_BE_SUB_ENTITY: {
81
+ 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.`,
82
+ params: ['relatedClientName', 'clientName'],
83
+ affectedFields: ['relatedClientId', 'relationshipTypeId', 'startingDate', 'endingDate'],
84
+ },
85
+ PARENT_ENTITY_TYPE_MISMATCH: {
86
+ message: `A parent entity must be the same entity type as the client during the relationship's timeframe. Please select a different relationship type or update either client's entity type.`,
87
+ affectedFields: ['relatedClientId', 'relationshipTypeId'],
88
+ },
89
+ CONSECUTIVE_DUPLICATE_RELATIONSHIPS: {
90
+ 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.`,
91
+ params: ['relationshipType', 'relatedClientName', 'clientName', 'relationshipEnding'],
92
+ affectedFields: ['startingDate', 'endingDate'],
93
+ },
94
+ SUBSIDIARY_CANNOT_HAVE_PARENT: {
95
+ 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.`,
96
+ params: ['clientName', 'parentClientName'],
97
+ affectedFields: ['relationshipTypeId', 'startingDate', 'endingDate'],
98
+ },
99
+ SUBSIDIARY_REQUIRES_FILES_SEPARATELY: {
100
+ message: `A subsidiary relationship can only be added to an entity that files separately. Please update the Sub/Parent status before adding a subsidiary relationship, or choose a different relationship type.`,
101
+ affectedFields: ['relationshipTypeId', 'filingTypeId'],
102
+ },
65
103
  };
@@ -667,6 +667,44 @@ export declare const VALIDATION_MESSAGES: {
667
667
  readonly message: "The related client has a close date that is the same as the relationship ending date, therefore the relationship must be marked as final. Please update the relationship's final status to 'Yes', or adjust the dates.";
668
668
  readonly affectedFields: readonly ["isFinal"];
669
669
  };
670
+ readonly CIRCULAR_RELATIONSHIP_DETECTED: {
671
+ readonly 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.";
672
+ readonly params: readonly ["clientName", "relatedClientName", "relationshipType"];
673
+ readonly affectedFields: readonly ["relationshipTypeId", "relatedClientId", "startingDate", "endingDate"];
674
+ };
675
+ readonly CONFLICTING_RELATIONSHIP_TYPES_SAME_TIMEFRAME: {
676
+ readonly 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.";
677
+ readonly params: readonly ["relatedClientName", "clientName"];
678
+ readonly affectedFields: readonly ["relationshipTypeId", "relatedClientId", "startingDate", "endingDate"];
679
+ };
680
+ readonly MULTIPLE_PARENT_RELATIONSHIPS_SAME_TIMEFRAME: {
681
+ readonly 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.";
682
+ readonly params: readonly ["parentRelatedClientName", "relationshipStarting"];
683
+ readonly affectedFields: readonly ["relationshipTypeId", "startingDate"];
684
+ };
685
+ readonly PARENT_CANNOT_BE_SUB_ENTITY: {
686
+ readonly 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.";
687
+ readonly params: readonly ["relatedClientName", "clientName"];
688
+ readonly affectedFields: readonly ["relatedClientId", "relationshipTypeId", "startingDate", "endingDate"];
689
+ };
690
+ readonly PARENT_ENTITY_TYPE_MISMATCH: {
691
+ readonly message: "A parent entity must be the same entity type as the client during the relationship's timeframe. Please select a different relationship type or update either client's entity type.";
692
+ readonly affectedFields: readonly ["relatedClientId", "relationshipTypeId"];
693
+ };
694
+ readonly CONSECUTIVE_DUPLICATE_RELATIONSHIPS: {
695
+ readonly 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.";
696
+ readonly params: readonly ["relationshipType", "relatedClientName", "clientName", "relationshipEnding"];
697
+ readonly affectedFields: readonly ["startingDate", "endingDate"];
698
+ };
699
+ readonly SUBSIDIARY_CANNOT_HAVE_PARENT: {
700
+ readonly 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.";
701
+ readonly params: readonly ["clientName", "parentClientName"];
702
+ readonly affectedFields: readonly ["relationshipTypeId", "startingDate", "endingDate"];
703
+ };
704
+ readonly SUBSIDIARY_REQUIRES_FILES_SEPARATELY: {
705
+ readonly message: "A subsidiary relationship can only be added to an entity that files separately. Please update the Sub/Parent status before adding a subsidiary relationship, or choose a different relationship type.";
706
+ readonly affectedFields: readonly ["relationshipTypeId", "filingTypeId"];
707
+ };
670
708
  };
671
709
  readonly FILING_CATEGORIES: {
672
710
  readonly INVALID_REQUEST: {
@@ -1 +1 @@
1
- {"version":3,"file":"validation-messages.d.ts","sourceRoot":"","sources":["../../src/validation/validation-messages.ts"],"names":[],"mappings":"AAoBA,eAAO,MAAM,mBAAmB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoBtB,CAAC"}
1
+ {"version":3,"file":"validation-messages.d.ts","sourceRoot":"","sources":["../../src/validation/validation-messages.ts"],"names":[],"mappings":"AAoBA,eAAO,MAAM,mBAAmB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoBtB,CAAC"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@forwardslashns/taskit-validation-messages",
3
- "version": "1.3.3",
3
+ "version": "1.3.5",
4
4
  "main": "dist/index.js",
5
5
  "types": "dist/index.d.ts",
6
6
  "type": "commonjs",
@@ -59,4 +59,42 @@ export const CLIENT_RELATIONSHIPS = {
59
59
  message: `The related client has a close date that is the same as the relationship ending date, therefore the relationship must be marked as final. Please update the relationship's final status to 'Yes', or adjust the dates.`,
60
60
  affectedFields: ['isFinal'],
61
61
  },
62
+ CIRCULAR_RELATIONSHIP_DETECTED: {
63
+ 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.`,
64
+ params: ['clientName', 'relatedClientName', 'relationshipType'],
65
+ affectedFields: ['relationshipTypeId', 'relatedClientId', 'startingDate', 'endingDate'],
66
+ },
67
+ CONFLICTING_RELATIONSHIP_TYPES_SAME_TIMEFRAME: {
68
+ 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.`,
69
+ params: ['relatedClientName', 'clientName'],
70
+ affectedFields: ['relationshipTypeId', 'relatedClientId', 'startingDate', 'endingDate'],
71
+ },
72
+ MULTIPLE_PARENT_RELATIONSHIPS_SAME_TIMEFRAME: {
73
+ 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.`,
74
+ params: ['parentRelatedClientName', 'relationshipStarting'],
75
+ affectedFields: ['relationshipTypeId', 'startingDate'],
76
+ },
77
+ PARENT_CANNOT_BE_SUB_ENTITY: {
78
+ 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.`,
79
+ params: ['relatedClientName', 'clientName'],
80
+ affectedFields: ['relatedClientId', 'relationshipTypeId', 'startingDate', 'endingDate'],
81
+ },
82
+ PARENT_ENTITY_TYPE_MISMATCH: {
83
+ message: `A parent entity must be the same entity type as the client during the relationship's timeframe. Please select a different relationship type or update either client's entity type.`,
84
+ affectedFields: ['relatedClientId', 'relationshipTypeId'],
85
+ },
86
+ CONSECUTIVE_DUPLICATE_RELATIONSHIPS: {
87
+ 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.`,
88
+ params: ['relationshipType', 'relatedClientName', 'clientName', 'relationshipEnding'],
89
+ affectedFields: ['startingDate', 'endingDate'],
90
+ },
91
+ SUBSIDIARY_CANNOT_HAVE_PARENT: {
92
+ 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.`,
93
+ params: ['clientName', 'parentClientName'],
94
+ affectedFields: ['relationshipTypeId', 'startingDate', 'endingDate'],
95
+ },
96
+ SUBSIDIARY_REQUIRES_FILES_SEPARATELY: {
97
+ message: `A subsidiary relationship can only be added to an entity that files separately. Please update the Sub/Parent status before adding a subsidiary relationship, or choose a different relationship type.`,
98
+ affectedFields: ['relationshipTypeId', 'filingTypeId'],
99
+ },
62
100
  } as const;