@grnsft/if 0.4.0 → 0.5.0

package/src/builtins/copy-param/README.md

@@ -0,0 +1,104 @@
+# Copy-param
+
+`copy-param` is a generic plugin that duplicates an existing parameter in the `input` data and assigns it to a new key. You can either keep or delete the original copied parameter. A common use case for this is to rename parameters in the `inputs` array.
+
+You provide the name of the value you want to copy, and a name to assign the copy to. You also toggle a `keep-existing` parameter to either persist or delete the original copied value.
+
+For example, you could copy `energy` into `energy-copy`, with `keep-existing=true`. In this case your inputs:
+
+```yaml
+- timestamp: "2023-12-12T00:00:13.000Z",
+  duration: 30,
+  energy: 30
+```
+
+would become
+
+```yaml
+- timestamp: "2023-12-12T00:00:13.000Z",
+  duration: 30,
+  energy: 30
+  energy-copy: 30
+```
+
+but with `keep-existing=false`, the same inputs would yield:
+
+```yaml
+- timestamp: "2023-12-12T00:00:13.000Z",
+  duration: 30,
+  energy-copy: 30
+```
+
+## Parameters
+
+### Config
+
+Three parameters are required in config: `from` and `to` and `keep-existing`.
+
+`from`: an array of strings. Each string should match an existing key in the `inputs` array
+`to`: a string defining the name to use to add the result of summing the input parameters to the output array.
+`keep-existing`: toggles whether to keep or delete the copied parameter (defined in `to`)
+
+### Inputs
+
+As with all plugins, `timestamp` and `duration` are required. The key passed to `from` must exist in the `input` data.
+
+## Returns
+
+The plugin adds a new parameter with the name defined in `to` to the `input` data.
+
+
+## Implementation
+
+To run the plugin, you must first create an instance of `Copy`. Then, you can call `execute()`.
+
+```typescript
+import { Copy } from ".";
+
+const plugin = Copy({ 'keep-existing': true, from: 'from-param', to: 'to-param' });
+
+const result = plugin.execute([{
+    timestamp: "2023-12-12T00:00:13.000Z",
+    duration: 30,
+    'from-param': 'hello',
+}])
+
+console.log(result)
+
+```
+
+## Example manifest
+
+IF users will typically call the plugin as part of a pipeline defined in a manifest file. In this case, instantiating the plugin is handled by and does not have to be done explicitly by the user. The following is an example manifest that calls `copy-param`:
+
+```yaml
+name: copy-param
+description:
+tags:
+initialize:
+  plugins:
+    copy-param:
+      path: builtin
+      method: Copy
+      global-config:
+        keep-existing: true
+        from: original
+        to: copy
+tree:
+  children:
+    child-1:
+      pipeline:
+        - copy-param
+      inputs:
+        - timestamp: "2023-12-12T00:00:00.000Z"
+          original: 'hello'
+
+```
+
+You can run this example by saving it as `./manifests/examples/copy.yml` and executing the following command from the project root:
+
+```sh
+if-run --manifest ./manifests/examples/copy.yml -s
+```
+
+The results will be displayed in the console.

package/src/builtins/csv-lookup/README.md

@@ -136,7 +136,45 @@ You can run this example by saving it as `./examples/manifests/csv-lookup.yml` a
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest manifests/plugins/csv-lookup.yml --output manifests/outputs/csv-lookup
+if-run --manifest manifests/plugins/csv-lookup.yml --output manifests/outputs/csv-lookup
 ```
 
 The results will be saved to a new `yaml` file in `manifests/outputs`.
+
+
+## Errors
+
+Coefficient exposes six of the IF error classes.
+
+### FetchingFileError
+
+This error is caused by problems finding the file at the path provided in the `filepath`. If the file is on your local filesystem, you can check that the file is definitely there. For a remote file, check your internet connection. You can check your connection to the server using a tool such as `ping` or `curl`. if you still experience problems, you could retrieve the remote file onto your local filesystem using a tool such as `wget`.
+
+### ReadFileError,
+
+This error is caused by problems reading the CSV file provided in the `filepath`. To fix it, check that the file contains valid CSV data. The file should have a `.csv` file extension and the data inside should be formatted correctly.
+
+### MissingCSVColumnError,
+
+This error is caused by `CsvLookup` failing to find a column in the CSV file whose name matches what was provided in `query`. To debug, check that you do not have any typos in your `query` and confirm that the requested column name definitely exists in the target file.
+
+### QueryDataNotFoundError,
+
+This error is caused by the `CsvLookup` plugin failing to find data that matches your query. Try revising your query parameters.
+
+### CSVParseError,
+
+This error arises due to problems parsing CSV data into IF. This can occur when the CSV data is incorrectly formatted or contains unexpected characters that IF does not recognize. These errors are expected to be unusual edge cases as incorrectly formatted data will usually be identified during file loading and cause a `ReadFileError`. To debug, check your CSV file for any unexpected formatting or unusual characters.
+
+### GlobalConfigError
+
+You will receive an error starting `GlobalConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
+
+The required parameters are:
+- `filepath`: This must be a path to a csv file
+- `query`: this must be an array of key-value pairs where the key is a string containing a column name an the value is a string containing the name of a value in `inputs`
+- `output`: this must be a string containing a name or a wildcard character (`"*"`)
+
+You can fix this error by checking you are providing valid values for each parameter in the config.
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/divide/README.md

@@ -4,8 +4,6 @@
 
 You provide the names of the values you want to divide, and a name to use to add the divide to the output array.
 
-For example, `boavizta-cpu` need `cpu/number-cores` to work, however `cloud-metadata` returns `vcpus-allocated`, to get number of cores you divide `vcpus-allocated` by 2.
-
 ## Parameters
 
 ### Plugin config
@@ -26,6 +24,8 @@ For example, `boavizta-cpu` need `cpu/number-cores` to work, however `cloud-meta
 
 The plugin throws an exception if the division result is not a number.
 
+>Note: Plugin will warn and return `numerator` value in case if `denominator` is zero.
+
 ## Calculation
 
 ```pseudocode
@@ -89,7 +89,33 @@ You can run this example by saving it as `./examples/manifests/divide.yml` and e
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest ./examples/manifests/divide.yml --output ./examples/outputs/divide.yml
+if-run --manifest ./examples/manifests/divide.yml --output ./examples/outputs/divide.yml
 ```
 
 The results will be saved to a new `yaml` file in `./examples/outputs`.
+
+## Errors
+
+`Divide` exposes two of IF's error classes.
+
+### GlobalConfigError
+
+You will receive an error starting `GlobalConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
+
+The required parameters are:
+- `numerator`: a string containing the name of the input parameter whose value should be divided by `denominator`
+- `denominator`: a number to use as the denominator
+- ``output`: a string containing the name to assign the result of the division
+
+You can fix this error by checking you are providing valid values for each parameter in the config.
+
+### `MissingInputDataError`
+
+This error arises when a necessary piece of input data is missing from the `inputs` array.
+Every element in the ``inputs` array must contain:
+- `timestamp`
+- `duration`
+- whatever value you passed to `numerator`
+
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/exponent/README.md

@@ -91,7 +91,27 @@ You can run this example by saving it as `manifests/examples/test/exponent.yml`
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest manifests/examples/test/exponent.yml --output manifests/outputs/exponent.yml
+if-run --manifest manifests/examples/test/exponent.yml --output manifests/outputs/exponent.yml
 ```
 
 The results will be saved to a new `yaml` file in `manifests/outputs`.
+
+## Errors
+
+`Exponent` exposes two of IF's error classes.
+
+### `MissingInputDataError`
+
+This error arises when a necessary piece of input data is missing from the `inputs` array.
+Every element in the `inputs` array must contain:
+
+- `timestamp`
+- `duration`
+- whatever value you passed to `input-parameter`
+
+
+### `InputValidationError`
+
+This error arises when an invalid value is passed to `Exponent`. Typically, this can occur when a non-numeric value (such as a string made of alphabetic characters) is passed where a number or numeric string is expected. Please check that the types are correct for all the relevant fields in your `inputs` array.
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/interpolation/README.md

@@ -164,5 +164,33 @@ You can execute this by passing it to `ie`. Run the impact using the following c
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest ./manifests/examples/interpolation.yml --output ./manifests/outputs/interpolation.yml
+if-run --manifest ./manifests/examples/interpolation.yml --output ./manifests/outputs/interpolation.yml
 ```
+
+## Errors
+
+`Interpolation` exposes one of IF's error classes.
+
+## `GlobalConfigError`
+
+### GlobalConfigError
+
+You will receive an error starting `GlobalConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
+
+The required parameters are:
+- `method`: a string containing either `linear`, `spline` or `polynomial`
+- `x`: an array of numbers
+- `y`: an array of numbers
+- `input-parameter`: a string containing the name of a value present in the `inputs` array'
+- `output-parameter`: a string
+
+You can fix this error by checking you are providing valid values for each parameter in the config.
+
+### Validation errors
+
+There are also several validation errors that can arise, including:
+- if the lengths of `x` and `y` are not equal
+- if `x` or `y` are empty
+- if the requested point to interpolate at is outside the range of `x`
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/mock-observations/README.md

@@ -91,7 +91,7 @@ You can run this example `manifest` by saving it as `manifests/plugins/mock-obse
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest ./examples/manifests/test/mock-observation.yml --output ./examples/outputs/mock-observation
+if-run --manifest ./examples/manifests/test/mock-observation.yml --output ./examples/outputs/mock-observation
 ```
 
 The results will be saved to a new `yaml` file in `./examples/outputs`.

package/src/builtins/multiply/README.md

@@ -88,7 +88,22 @@ You can run this example by saving it as `./examples/manifests/test/multiply.yml
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest ./examples/manifests/test/multiply.yml --output ./examples/outputs/multiply.yml
+if-run --manifest ./examples/manifests/test/multiply.yml --output ./examples/outputs/multiply.yml
 ```
 
 The results will be saved to a new `yaml` file in `./examples/outputs`
+
+
+## Errors
+
+`Multiply` uses one of the IF error classes.
+
+### `MissingInputDataError`
+
+This error arises when a necessary piece of input data is missing from the `inputs` array.
+Every element in the `inputs` array must contain:
+- `timestamp`
+- `duration`
+- whatever values you passed to `input-parameters`
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/regex/README.md

@@ -4,8 +4,6 @@
 
 You provide the name of the value you want to match, and a name to use to add the regex to the output array.
 
-For example, `boavizta-cpu` need `cpu/name` to work, however `cloud-metadata` returns `physical-processor` which usually contains a long string of processors that the instance could be separated by `,`, like so:
-
 ```
 Intel® Xeon® Platinum 8272CL,Intel® Xeon® 8171M 2.1 GHz,Intel® Xeon® E5-2673 v4 2.3 GHz,Intel® Xeon® E5-2673 v3 2.4 GHz
 ```
@@ -89,3 +87,35 @@ if --manifest manifests/examples/regex.yml --output manifests/outputs/regex.yml
 ```
 
 The results will be saved to a new `yaml` file in `manifests/outputs`.
+
+## Errors
+
+`Regex` uses three of IF's error classes:
+
+### `MissingInputDataError`
+
+This error arises when a necessary piece of input data is missing from the `inputs` array.
+Every element in the `inputs` array must contain:
+- `timestamp`
+- `duration`
+- whatever value you passed to `parameter`
+
+
+### `GlobalConfigError`
+
+You will receive an error starting `GlobalConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
+
+The required parameters are:
+
+- `parameter`: a string containing the name of a value in the inputs array
+- `match`: a valid regex pattern
+- `output`: a string
+
+You can fix this error by checking you are providing valid values for each parameter in the config.
+
+
+### `RegexMismatchError`
+
+This error arises when the requested regex cannot find any matches in the given data. If there are multiple matches, the plugin returns the first, but if there are none, it throws this error.
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/sci/README.md

@@ -19,6 +19,8 @@
 
 - `sci`: carbon expressed in terms of the given functional unit
 
+>Note: Plugin will warn and return `carbon` value in case if `functional-unit`'s value is zero.
+
 ## Calculation
 
 SCI is calculated as:
@@ -83,7 +85,28 @@ You can run this example `manifest` by saving it as `./manifests/plugins/sci.yml
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest manifests/plugins/sci.yml --output manifests/outputs/sci.yml
+if-run --manifest manifests/plugins/sci.yml --output manifests/outputs/sci.yml
 ```
 
 The results will be saved to a new `yaml` file.
+
+## Errors
+
+`SCI` uses one of the IF error classes.
+
+### `MissingInputDataError`
+
+This error arises when a necessary piece of input data is missing from the `inputs` array.
+
+Every element in the `inputs` array must contain:
+- `timestamp`
+- `duration`
+- `carbon`: a numeric value named `carbon` must exist in the inputs array
+- whatever value you passed to `functional-unit`
+
+
+### Validation errors
+
+There is also a validation step that checks that the `functional-unit` was provided in the plugin config. If you see an error reporting this value as missing, please check you have provided it.
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/sci-embodied/README.md

@@ -104,7 +104,21 @@ You can run this example `manifest` by executing the following command from the
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest manifests/plugins/sci-embodied.yml --output manifests/outputs/sci-embodied.yml
+if-run --manifest manifests/plugins/sci-embodied.yml --output manifests/outputs/sci-embodied.yml
 ```
 
 The results will be saved to a new `yaml` file in `./examples/outputs`.
+
+
+## Errors
+
+`SciEmbodied` uses one of IF's error classes
+
+### `SciEmbodiedError`
+
+This error class is used to describe a problem with one of the input values to `sci-embodied`. This is typically due to an incorrect type or a reference to a value that is not available.
+
+You will receive a specific error message explaining which parameter is problematic, and you can check and replace where appropriate.
+
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/shell/README.md

@@ -124,7 +124,18 @@ You can run this example `manifest` by saving it as `manifests/plugins/shell.yml
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest manifests/plugins/shell.yml --output manifests/outputs/shell.yml
+if-run --manifest manifests/plugins/shell.yml --output manifests/outputs/shell.yml
 ```
 
 The results will be saved to a new `yaml` file.
+
+
+## Errors
+
+`Shell` uses one of the error classes provided by IF
+
+### `ProcessExecutionError`
+
+This error is thrown when the program invoked in the spawned shell fails for some reason that is not known to IF. Since the shell executes arbitrary code, it is difficult for IF to provide specific errors - this is delegated to the developers of the executed program.
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/subtract/README.md

@@ -88,7 +88,18 @@ You can run this example by saving it as `./examples/manifests/test/subrtact.yml
 
 ```sh
 npm i -g @grnsft/if
-ie --manifest /manifests/plugins/subtract.yml --output manifests/outputs/subtract.yml
+if-run --manifest /manifests/plugins/subtract.yml --output manifests/outputs/subtract.yml
 ```
 
 The results will be saved to a new `yaml` file in `manifests/outputs`.
+
+
+## Errors
+
+`Subtract` uses one of IF's error classes:
+
+### `InputValidationError`
+
+This error arises when an invalid value is passed to `Subtract`. Typically, this can occur when a non-numeric value (such as a string made of alphabetic characters) is passed where a number or numeric string is expected. Please check that the types are correct for all the relevant fields in your `inputs` array.
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors

package/src/builtins/sum/README.md

@@ -85,7 +85,34 @@ tree:
 You can run this example by saving it as `./examples/manifests/sum.yml` and executing the following command from the project root:
 
 ```sh
-ie --manifest ./examples/manifests/sum.yml --output ./examples/outputs/sum.yml
+if-run --manifest ./examples/manifests/sum.yml --output ./examples/outputs/sum.yml
 ```
 
 The results will be saved to a new `yaml` file in `./examples/outputs`.
+
+
+## Errors
+
+`Sum` exposes two of the IF error classes.
+
+### GlobalConfigError
+
+You will receive an error starting `GlobalConfigError: ` if you have not provided the expected configuration data in the plugin's `initialize` block.
+
+The required parameters are:
+- `input-parameters`: this must be an array of strings, each being the name of a value in the `inputs` array
+- `output-parameter`: this must be a string
+
+You can fix this error by checking you are providing valid values for each parameter in the config.
+
+### `MissingInputDataError`
+
+This error arises when a necessary piece of input data is missing from the `inputs` array.
+Every element in the ``inputs` array must contain:
+
+- `timestamp`
+- `duration`
+- whatever values you passed to `input-parameters`
+
+
+For more information on our error classes, please visit [our docs](https://if.greensoftware.foundation/reference/errors).

package/src/config/env-template.yml

@@ -0,0 +1,24 @@
+name: template manifest # rename me!
+description: auto-generated template # update description!
+tags: # add any tags that will help you to track your manifests
+initialize:
+  outputs:
+    - yaml # you can add - csv to export to csv
+  plugins: # add more plugins for your use-case
+    memory-energy-from-memory-util: # you can name this any way you like!
+      method: Coefficient # the name of the function exported from the plugin
+      path: "builtin" # the import path
+      global-config: # anmy config required by the plugin
+        input-parameter: "memory/utilization"
+        coefficient: 0.0001 #kwH/GB
+        output-parameter: "memory/energy"
+tree:
+  children: # add a chile for each distinct component you want to measure
+    child:
+      pipeline: # the pipeline is an ordered list of plugins you want to execute
+        - memory-energy-from-memory-util # must match the name in initialize!
+      config: # any plugin specific, node-level config
+      inputs:
+        - timestamp: 2023-12-12T00:00:00.000Z # ISO 8061 string
+          duration: 3600 # units of seconds
+          memory/utilization: 10

package/build/builtins/coefficient/types.d.ts

@@ -1,5 +0,0 @@
-export type CoefficientConfig = {
-    'input-parameter': string;
-    coefficient: number;
-    'output-parameter': string;
-};

package/build/builtins/coefficient/types.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoidHlwZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi9zcmMvYnVpbHRpbnMvY29lZmZpY2llbnQvdHlwZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6IiIsInNvdXJjZXNDb250ZW50IjpbImV4cG9ydCB0eXBlIENvZWZmaWNpZW50Q29uZmlnID0ge1xuICAnaW5wdXQtcGFyYW1ldGVyJzogc3RyaW5nO1xuICBjb2VmZmljaWVudDogbnVtYmVyO1xuICAnb3V0cHV0LXBhcmFtZXRlcic6IHN0cmluZztcbn07XG4iXX0=

package/build/builtins/exponent/types.d.ts

@@ -1,5 +0,0 @@
-export type ExponentConfig = {
-    'input-parameter': string;
-    exponent: number;
-    'output-parameter': string;
-};

package/build/builtins/exponent/types.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoidHlwZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi9zcmMvYnVpbHRpbnMvZXhwb25lbnQvdHlwZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6IiIsInNvdXJjZXNDb250ZW50IjpbImV4cG9ydCB0eXBlIEV4cG9uZW50Q29uZmlnID0ge1xuICAnaW5wdXQtcGFyYW1ldGVyJzogc3RyaW5nO1xuICBleHBvbmVudDogbnVtYmVyO1xuICAnb3V0cHV0LXBhcmFtZXRlcic6IHN0cmluZztcbn07XG4iXX0=

package/build/builtins/interpolation/types.d.ts

@@ -1,5 +0,0 @@
-export declare enum Method {
-    LINEAR = "linear",
-    SPLINE = "spline",
-    POLYNOMIAL = "polynomial"
-}

package/build/builtins/interpolation/types.js

@@ -1,10 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Method = void 0;
-var Method;
-(function (Method) {
-    Method["LINEAR"] = "linear";
-    Method["SPLINE"] = "spline";
-    Method["POLYNOMIAL"] = "polynomial";
-})(Method || (exports.Method = Method = {}));
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoidHlwZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi9zcmMvYnVpbHRpbnMvaW50ZXJwb2xhdGlvbi90eXBlcy50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOzs7QUFBQSxJQUFZLE1BSVg7QUFKRCxXQUFZLE1BQU07SUFDaEIsMkJBQWlCLENBQUE7SUFDakIsMkJBQWlCLENBQUE7SUFDakIsbUNBQXlCLENBQUE7QUFDM0IsQ0FBQyxFQUpXLE1BQU0sc0JBQU4sTUFBTSxRQUlqQiIsInNvdXJjZXNDb250ZW50IjpbImV4cG9ydCBlbnVtIE1ldGhvZCB7XG4gIExJTkVBUiA9ICdsaW5lYXInLFxuICBTUExJTkUgPSAnc3BsaW5lJyxcbiAgUE9MWU5PTUlBTCA9ICdwb2x5bm9taWFsJyxcbn1cbiJdfQ==

package/build/builtins/mock-observations/types.d.ts

@@ -1,13 +0,0 @@
-import { DateTime } from 'luxon';
-import { Generator } from './interfaces/index';
-export type ObservationParams = {
-    duration: number;
-    timeBucket: DateTime;
-    component: Record<string, string>;
-    generators: Generator[];
-};
-export type RandIntGeneratorParams = {
-    name: string;
-    min: number;
-    max: number;
-};

package/build/builtins/mock-observations/types.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoidHlwZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi9zcmMvYnVpbHRpbnMvbW9jay1vYnNlcnZhdGlvbnMvdHlwZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6IiIsInNvdXJjZXNDb250ZW50IjpbImltcG9ydCB7RGF0ZVRpbWV9IGZyb20gJ2x1eG9uJztcblxuaW1wb3J0IHtHZW5lcmF0b3J9IGZyb20gJy4vaW50ZXJmYWNlcy9pbmRleCc7XG5cbmV4cG9ydCB0eXBlIE9ic2VydmF0aW9uUGFyYW1zID0ge1xuICBkdXJhdGlvbjogbnVtYmVyO1xuICB0aW1lQnVja2V0OiBEYXRlVGltZTtcbiAgY29tcG9uZW50OiBSZWNvcmQ8c3RyaW5nLCBzdHJpbmc+O1xuICBnZW5lcmF0b3JzOiBHZW5lcmF0b3JbXTtcbn07XG5cbmV4cG9ydCB0eXBlIFJhbmRJbnRHZW5lcmF0b3JQYXJhbXMgPSB7XG4gIG5hbWU6IHN0cmluZztcbiAgbWluOiBudW1iZXI7XG4gIG1heDogbnVtYmVyO1xufTtcbiJdfQ==

package/build/builtins/multiply/types.d.ts

@@ -1,4 +0,0 @@
-export type MultiplyConfig = {
-    'input-parameters': string[];
-    'output-parameter': string;
-};

package/build/builtins/multiply/types.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoidHlwZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi9zcmMvYnVpbHRpbnMvbXVsdGlwbHkvdHlwZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6IiIsInNvdXJjZXNDb250ZW50IjpbImV4cG9ydCB0eXBlIE11bHRpcGx5Q29uZmlnID0ge1xuICAnaW5wdXQtcGFyYW1ldGVycyc6IHN0cmluZ1tdO1xuICAnb3V0cHV0LXBhcmFtZXRlcic6IHN0cmluZztcbn07XG4iXX0=

package/build/builtins/subtract/types.d.ts

@@ -1,4 +0,0 @@
-export type SubtractConfig = {
-    'input-parameters': string[];
-    'output-parameter': string;
-};

package/build/builtins/subtract/types.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoidHlwZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi9zcmMvYnVpbHRpbnMvc3VidHJhY3QvdHlwZXMudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6IiIsInNvdXJjZXNDb250ZW50IjpbImV4cG9ydCB0eXBlIFN1YnRyYWN0Q29uZmlnID0ge1xuICAnaW5wdXQtcGFyYW1ldGVycyc6IHN0cmluZ1tdO1xuICAnb3V0cHV0LXBhcmFtZXRlcic6IHN0cmluZztcbn07XG4iXX0=

package/build/builtins/sum/types.d.ts

@@ -1,4 +0,0 @@
-export type SumConfig = {
-    'input-parameters': string[];
-    'output-parameter': string;
-};

package/build/builtins/sum/types.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoidHlwZXMuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi9zcmMvYnVpbHRpbnMvc3VtL3R5cGVzLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiIiLCJzb3VyY2VzQ29udGVudCI6WyJleHBvcnQgdHlwZSBTdW1Db25maWcgPSB7XG4gICdpbnB1dC1wYXJhbWV0ZXJzJzogc3RyaW5nW107XG4gICdvdXRwdXQtcGFyYW1ldGVyJzogc3RyaW5nO1xufTtcbiJdfQ==

package/build/types/common.d.ts

@@ -1,4 +0,0 @@
-export type KeyValuePair = {
-    [key: string]: any;
-};
-export type ConfigParams = Record<string, any>;

package/build/types/common.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiY29tbW9uLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vLi4vc3JjL3R5cGVzL2NvbW1vbi50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiIiwic291cmNlc0NvbnRlbnQiOlsiZXhwb3J0IHR5cGUgS2V5VmFsdWVQYWlyID0ge1xuICBba2V5OiBzdHJpbmddOiBhbnk7XG59O1xuXG5leHBvcnQgdHlwZSBDb25maWdQYXJhbXMgPSBSZWNvcmQ8c3RyaW5nLCBhbnk+O1xuIl19

package/build/types/group-by.d.ts

@@ -1,3 +0,0 @@
-export type GroupByConfig = {
-    group: string[];
-};

package/build/types/group-by.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiZ3JvdXAtYnkuanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi9zcmMvdHlwZXMvZ3JvdXAtYnkudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6IiIsInNvdXJjZXNDb250ZW50IjpbImV4cG9ydCB0eXBlIEdyb3VwQnlDb25maWcgPSB7XG4gIGdyb3VwOiBzdHJpbmdbXTtcbn07XG4iXX0=

package/build/types/helpers.d.ts

@@ -1,4 +0,0 @@
-export type ErrorFormatParams = {
-    scope?: string;
-    message: string;
-};

package/build/types/helpers.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiaGVscGVycy5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy90eXBlcy9oZWxwZXJzLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiIiLCJzb3VyY2VzQ29udGVudCI6WyJleHBvcnQgdHlwZSBFcnJvckZvcm1hdFBhcmFtcyA9IHtcbiAgc2NvcGU/OiBzdHJpbmc7XG4gIG1lc3NhZ2U6IHN0cmluZztcbn07XG4iXX0=