@trackunit/iris-app-api 1.7.42 → 1.7.43-alpha-fb1493a185d.0

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@trackunit/iris-app-api",
3
- "version": "1.7.42",
3
+ "version": "1.7.43-alpha-fb1493a185d.0",
4
4
  "license": "SEE LICENSE IN LICENSE.txt",
5
5
  "repository": "https://github.com/Trackunit/manager",
6
6
  "engines": {
@@ -4,12 +4,12 @@ export interface AssetHomeExtensionManifest extends AbstractExtensionManifest {
4
4
  type: "ASSET_HOME_EXTENSION";
5
5
  /**
6
6
  * Conditions for the asset home extension to be shown.
7
- * model and brand is case insensitive so does not matter how you write the brand.
7
+ * model, brand, and telematicsDeviceType are case insensitive so does not matter how you write them.
8
8
  * brand: "trackunit" and brand: "Trackunit" will be the same.
9
9
  *
10
10
  * Its doing AND between the conditions types and OR between the conditions of the same type:
11
11
  * - If both model and brand are used/filled out then asset needs to match both model and brand.
12
- * - If only brand or model is used/filled out then the asset needs to match the filled out property.
12
+ * - If only brand, model, or telematicsDeviceType is used/filled out then the asset needs to match the filled out property.
13
13
  * - If only scopes is used/filled out then the asset home extension will be shown for all assets that the user has the required scopes for.
14
14
  * - If more scopes are used/filled out then the asset home extension will be shown for all assets that the user has one of the required scopes for.
15
15
  * - If no conditions are used/filled out then the asset home extension will be shown for all assets.
@@ -17,6 +17,7 @@ export interface AssetHomeExtensionManifest extends AbstractExtensionManifest {
17
17
  conditions?: {
18
18
  model?: Array<string | RegExpType> | string | RegExpType;
19
19
  brand?: Array<string | RegExpType> | string | RegExpType;
20
+ telematicsDeviceType?: Array<string | RegExpType> | string | RegExpType;
20
21
  scopes?: AccountScope | Array<AccountScope>;
21
22
  /**
22
23
  * Only entityType ASSET custom fields are supported here
@@ -1 +1 @@
1
- {"version":3,"file":"assetHomeExtensionManifest.js","sourceRoot":"","sources":["../../../../../../../libs/iris-app-sdk/iris-app-api/src/types/extensions/assetHomeExtensionManifest.ts"],"names":[],"mappings":"","sourcesContent":["import {\n AbstractExtensionManifest,\n RegExpType,\n RequiredCustomField,\n TranslationKey,\n Translations,\n} from \"../irisAppExtensionManifest\";\nimport { AccountScope } from \"../scopes\";\n\nexport interface AssetHomeExtensionManifest extends AbstractExtensionManifest {\n type: \"ASSET_HOME_EXTENSION\";\n /**\n * Conditions for the asset home extension to be shown.\n * model and brand is case insensitive so does not matter how you write the brand.\n * brand: \"trackunit\" and brand: \"Trackunit\" will be the same.\n *\n * Its doing AND between the conditions types and OR between the conditions of the same type:\n * - If both model and brand are used/filled out then asset needs to match both model and brand.\n * - If only brand or model is used/filled out then the asset needs to match the filled out property.\n * - If only scopes is used/filled out then the asset home extension will be shown for all assets that the user has the required scopes for.\n * - If more scopes are used/filled out then the asset home extension will be shown for all assets that the user has one of the required scopes for.\n * - If no conditions are used/filled out then the asset home extension will be shown for all assets.\n */\n conditions?: {\n model?: Array<string | RegExpType> | string | RegExpType;\n brand?: Array<string | RegExpType> | string | RegExpType;\n scopes?: AccountScope | Array<AccountScope>;\n\n /**\n * Only entityType ASSET custom fields are supported here\n */\n requiredCustomField?: RequiredCustomField | Array<RequiredCustomField>;\n };\n menuItem: {\n name: string | Translations | TranslationKey;\n };\n}\n"]}
1
+ {"version":3,"file":"assetHomeExtensionManifest.js","sourceRoot":"","sources":["../../../../../../../libs/iris-app-sdk/iris-app-api/src/types/extensions/assetHomeExtensionManifest.ts"],"names":[],"mappings":"","sourcesContent":["import {\n AbstractExtensionManifest,\n RegExpType,\n RequiredCustomField,\n TranslationKey,\n Translations,\n} from \"../irisAppExtensionManifest\";\nimport { AccountScope } from \"../scopes\";\n\nexport interface AssetHomeExtensionManifest extends AbstractExtensionManifest {\n type: \"ASSET_HOME_EXTENSION\";\n /**\n * Conditions for the asset home extension to be shown.\n * model, brand, and telematicsDeviceType are case insensitive so does not matter how you write them.\n * brand: \"trackunit\" and brand: \"Trackunit\" will be the same.\n *\n * Its doing AND between the conditions types and OR between the conditions of the same type:\n * - If both model and brand are used/filled out then asset needs to match both model and brand.\n * - If only brand, model, or telematicsDeviceType is used/filled out then the asset needs to match the filled out property.\n * - If only scopes is used/filled out then the asset home extension will be shown for all assets that the user has the required scopes for.\n * - If more scopes are used/filled out then the asset home extension will be shown for all assets that the user has one of the required scopes for.\n * - If no conditions are used/filled out then the asset home extension will be shown for all assets.\n */\n conditions?: {\n model?: Array<string | RegExpType> | string | RegExpType;\n brand?: Array<string | RegExpType> | string | RegExpType;\n telematicsDeviceType?: Array<string | RegExpType> | string | RegExpType;\n scopes?: AccountScope | Array<AccountScope>;\n\n /**\n * Only entityType ASSET custom fields are supported here\n */\n requiredCustomField?: RequiredCustomField | Array<RequiredCustomField>;\n };\n menuItem: {\n name: string | Translations | TranslationKey;\n };\n}\n"]}