Simplified API for custom types

documentation/kinds/custom-types.md

@@ -57,7 +57,7 @@ In the example above, calling `matrix2x3.properties.width` is supported by auto-
 ### Uniqueness
 
 Typir ensures uniqueness for custom types.
-Two custom types are unique, if their identifiers are the same (this counts for any type, not only for custom types).
+Two custom types are identical, if their identifiers are the same (this counts for any type, not only for custom types).
 The default implementation calculates the identifier by concatenating the values of all properties.
 
 ### Circular dependencies

packages/typir/test/kinds/custom/custom-example-matrix.test.ts

@@ -20,7 +20,7 @@ import { assertTypirType } from '../../../src/utils/utils.js';
  * The custom type called "Matrix" represents a two-dimensional array of primitive types.
  * Known from mathematics, the "width" represents the number of columns and the "height" the number of row of a matrix.
  *
- * This TypeScript type specifies the properties of the the Typir types which represent "matrices".
+ * This TypeScript type specifies the properties of the Typir types which represent "matrices".
  */
 export type MatrixType = { // "interface" instead of "type" does not work!
     baseType: PrimitiveType;

packages/typir/test/kinds/custom/custom-example-restricted.test.ts

@@ -18,7 +18,7 @@ import { createTypirServicesForTesting, expectToBeType } from '../../../src/util
  * The custom type called "RestrictedInteger" represents a primitive integer type with an upper bound,
  * i.e. it looks like usual integers, but integer values/literals higher than the upper bound cannot be assigned to the restricted integer.
  *
- * This TypeScript type specifies the properties of the the Typir types which represent "restricted integers".
+ * This TypeScript type specifies the properties of the Typir types which represent "restricted integers".
  */
 export type RestrictedInteger = {
     upperBound: number;

packages/typir/test/kinds/custom/custom-independent.test.ts

@@ -11,7 +11,7 @@ import { TestLanguageNode } from '../../../src/test/predefined-language-nodes.js
 import { TypirServices } from '../../../src/typir.js';
 import { createTypirServicesForTesting, expectTypirTypes } from '../../../src/utils/test-utils.js';
 
-// These test cases test, that it is possible to work with two different kinds of custom types independent from each other in the same Typir instance,
+// These test cases test that it is possible to work with two different kinds of custom types independent from each other in the same Typir instance,
 // even when these custom types/kinds have the same properties!
 
 export type MyCustomType1 = {

packages/typir/test/kinds/custom/custom-nested-properties.test.ts

@@ -12,7 +12,7 @@ import { TestLanguageNode } from '../../../src/test/predefined-language-nodes.js
 import { TypirServices } from '../../../src/typir.js';
 import { createTypirServicesForTesting } from '../../../src/utils/test-utils.js';
 
-// These test cases test, that nesting of properties for custom types is possible (including recursion).
+// These test cases test that nesting of properties for custom types is possible (including recursion).
 
 export type NestedProperty = {
     myBool: boolean;
@@ -58,7 +58,7 @@ describe('Check that nested properties for custom types work', () => {
         const customKind = new CustomKind<Properties, TestLanguageNode>(typir, {
             name: 'MyCustom',
             /** Compared with the test case above, this calculation creates the same identifiers, since it does not take the deeper nesting into account.
-             * For these independent test cases, this is now problem.
+             * For these independent test cases, this is no problem.
              * But if both kinds are used together in the same Typir instance, the calculation of type identifiers need to be different for both kinds in order to produce unique identifiers.
              */
             calculateTypeIdentifier: properties => `mycustom-${properties.nested.deeper.myBool}-${typir.infrastructure.TypeResolver.resolve(properties.nested.deeper.myType).getIdentifier()}`,

packages/typir/test/kinds/custom/custom-selectors.test.ts

@@ -11,7 +11,7 @@ import { TestExpressionNode, TestLanguageNode } from '../../../src/test/predefin
 import { TypirServices } from '../../../src/typir.js';
 import { createTypirServicesForTesting } from '../../../src/utils/test-utils.js';
 
-// These test cases test, that all possible TypeSelectors work for custom types.
+// These test cases test that all possible TypeSelectors work for custom types.
 
 export type MyCustomProperties = {
     dependsOnType?: CustomType<MyCustomProperties, TestLanguageNode>;