@grnsft/if 0.5.0-beta.0 → 0.6.0-beta.0

package/README.md

@@ -19,7 +19,7 @@ Read the [specification and design docs](https://if.greensoftware.foundation) to
 
 ## Get started
 
-IF is a framework for running pipelines of plugins that operate on a set of observations. This is all configured using a manifest file.  We provide a standard library of plugins that come bundled with IF - we refer to these as `builtins`. We also have an [Explorer](https://explorer.if.greensoftware.foundation) where anyone can list third party plugins you can install.
+IF is a framework for running pipelines of plugins that operate on a set of observations. This is all configured using a manifest file. We provide a standard library of plugins that come bundled with IF - we refer to these as `builtins`. We also have an [Explorer](https://explorer.if.greensoftware.foundation) where anyone can list third party plugins you can install.
 
 Start by installing the latest version of IF:
 
@@ -32,26 +32,18 @@ Then create a `manifest` file that describes your application (see our docs for
 Then, run `if` using the following command:
 
 ```sh
-if-run --manifest <path-to-your-manifest-file> --stdout
-## or you can use aliases
-if-run -m <path-to-your-manifest-file> -s
+if-run --manifest <path-to-your-manifest-file>
+## or you can use alias
+if-run -m <path-to-your-manifest-file>
 
 ```
 
-Note that above command will print your outputs to the console. You can also provide the `--output` command to save your outputs to a yaml file:
+Note that above command will print your outputs to the console. If you do not want to print the outputs to the console, you need to provide `--no-output` command. You can also provide the `--output` command to save your outputs to a yaml file:
 
 ```sh
 if-run -m <path-to-your-manifest> -o <savepath>
 ```
 
-Note that you also have to add configuration to your manifest to enable this, as follows:
-
-```yaml
-initialize:
-  output:
-    - yaml
-```
-
 The `if-run` CLI tool will configure and run the plugins defined in your input `yaml` (`manifest`) and return the results as an output `yaml` (`output`).
 
 Use the `debug` command if you want to diagnose and fix errors in your plugin:
@@ -72,19 +64,16 @@ if-run -h
 
 Please read our documentation at [if.greensoftware.foundation](https://if.greensoftware.foundation/)
 
-
 ## Video walk-through
 
 Watch this video to learn how to create and run a `manifest`.
 
 [![Watch the walk-through video](https://i3.ytimg.com/vi/R-6eDM8AsvY/maxresdefault.jpg)](https://youtu.be/GW37Qd4AQbU)
 
-
 ## Join our mailing list
 
 We have a public mailing list at [if-community@greensoftware.foundation](https://groups.google.com/u/1/a/greensoftware.foundation/g/if-community). We send out weekly updates that explain what we've shipped, what we're working on and how you can get involved each week!
 
-
 ## Contributing
 
 To contribute to IF, please fork this repository and raise a pull request from your fork.
@@ -93,7 +82,6 @@ You can check our issue board for issues. We mark some issues `core-only` if the
 
 Please read the full contribution guidelines at [if.greensoftware.foundation](https://if.greensoftware.foundation/Contributing)
 
-
 ## Bug reports
 
 To report bugs please use our bug report template. You can do this by opening a new issue and selecting `Bug Report` when you are prompted to pick a template. The more information you provide,.the quicker we will be able to reproduce, diagnose and triage your issue.

package/Refactor-migration-guide.md

@@ -8,43 +8,29 @@ If you are a IF user or developer, there are some changes you must be aware of r
 
 There have been some name changes to the CLI, specifically:
 
-- `impact-engine` --> `ie`
-    The command line tool has been renamed from `impact-engine` to simply `ie`. This means that to invoke the Impact Framework on the command line you simply use 
+- `impact-engine` --> `if-run`
+  The command line tool has been renamed from `impact-engine` to simply `if-run`. This means that to invoke the Impact Framework on the command line you simply use
 
-    ```
-    if-run ...
-    ```
--  `impl` --> `manifest` 
-    We have deprecated the original `impl` and `ompl` terminology across all our repositories and on the command line. Now, to pass a manifest file to IF, you use the `--manifest` command, as follows:
+  ```
+  if-run ...
+  ```
 
-    ```sh
-    if-run --manifest <path-to-manifest>
-    ```
+- `impl` --> `manifest`
+  We have deprecated the original `impl` and `ompl` terminology across all our repositories and on the command line. Now, to pass a manifest file to IF, you use the `--manifest` command, as follows:
 
+  ```sh
+  if-run --manifest <path-to-manifest>
+  ```
 
 - `ompl` --> `output`
- 
-    We have deprecated the original `impl` and `ompl` terminology across all our repositories and on the command line. Now, to define a savepath for your output file, you use the `--output` command, as follows:
 
-    ```sh
-    if-run --manifest <path-to-manifest> --output <savepath>
-    ```
+  We have deprecated the original `impl` and `ompl` terminology across all our repositories and on the command line. Now, to define a savepath for your output file, you use the `--output` command, as follows:
 
-## Outputs
+  ```sh
+  if-run --manifest <path-to-manifest> --output <savepath>
+  ```
 
-We currently default to exporting output data to the console only. If you want to export to a file, you have to add a small piece of config inside your manifest, as follows:
-
-```yaml
-initalize:
-  plugins: ...
-  outputs: ['yaml']
-```
-
-You then provide your savepatrh (without file extension) to the `--output` command on the CLI.
-
-The available options are currently `csv`, `yaml` or `log`.
-
-### Summary of how to run the refactored IF 
+### Summary of how to run the refactored IF
 
 As before, you can install IF from our npm package using
 
@@ -64,7 +50,6 @@ This will dump the output to the console. If you want to save the output to a ya
 if-run --manifest <path-to-manifest> --output <savepath>
 ```
 
-
 If you want to clone the source code and install and run a local copy of IF, you can do so using:
 
 ```sh
@@ -76,138 +61,136 @@ npm i
 Then run IF using the following command:
 
 ```sh
-npm run if -- --manifest <path-to-manifest>
+npm run if-run -- --manifest <path-to-manifest>
 ```
 
-
 ## Manifest files
 
 There have also been some changes to the structure of manifest files. Some of these are simple renaming changes, others are more functional.
 
 - **Rename `graph` -> `tree`**
-    The `graph` section of the manifest file is now renamed to `tree`. This is just to help us stay consistent in our metaphors and provide a more familiar naming convention for the data beneath.
+  The `graph` section of the manifest file is now renamed to `tree`. This is just to help us stay consistent in our metaphors and provide a more familiar naming convention for the data beneath.
 
 - **Use plugin name as key in `Initialize` block**
-    In the previous version of IF, the plugins were organized into an array each having a `name` key, with the plugin name as the value. In the refactored IF, we use the name as the key identifying the plugin. For example, this is the OLD way:
-    
-    ```yaml
-    initialize:
-      plugins:
-        - name: ccf
-          model: CloudCarbonFootprint
-          path: if-plugins
-    ```
-
-    This is the new way:
-    
-    ```yaml
-    initialize:
-      plugins:
-        "sci-e":
-          path: "@grnsft/if-plugins"
-          method: SciE
-    ```
+  In the previous version of IF, the plugins were organized into an array each having a `name` key, with the plugin name as the value. In the refactored IF, we use the name as the key identifying the plugin. For example, this is the OLD way:
+
+  ```yaml
+  initialize:
+    plugins:
+      - name: ccf
+        model: CloudCarbonFootprint
+        path: if-plugins
+  ```
+
+  This is the new way:
+
+  ```yaml
+  initialize:
+    plugins:
+      'sci-e':
+        path: '@grnsft/if-plugins'
+        method: SciE
+  ```
 
 - **Rename `model` to `method` in `Initialize` block**
-    Each plugin in the initialize block 
-
-    Each plugin in the `Initialize` block has a field where the name of the exported function representing that plugin is defined. Previously, these were class names and they were defined using the `model` key. Now, they are functions, and they are defined using the `method` key. We use `method` instead of `function` because `function` is a reserved keyword in Typescript.
-    
-    For example:
-    
-    ```yaml
-    "sci-embodied":
-      path: "builtin"
-      method: SciEmbodied
-    ```
+  Each plugin in the initialize block
+
+  Each plugin in the `Initialize` block has a field where the name of the exported function representing that plugin is defined. Previously, these were class names and they were defined using the `model` key. Now, they are functions, and they are defined using the `method` key. We use `method` instead of `function` because `function` is a reserved keyword in Typescript.
+
+  For example:
+
+  ```yaml
+  'sci-embodied':
+    path: 'builtin'
+    method: SciEmbodied
+  ```
 
 - **Global config**
-    We have introduced the concept of global config to the plugins. This is truly global configuration data that should be kept constant regardless of where the plugin is invoked across the manifest file. 
-    
-    A good example is the `interpolation` method to use in the Teads curve plugin - this is not expected to vary from component to component and can therefore be defined in global config. The plugin code itself must expect the global config. Then, the config can be passed in the `Initialize` block, for example:
-    
-    ```yaml
-    initialize:
-      plugins:
-        "time-sync":
-           method: TimeSync
-           path: "builtin"
-           global-config:
-             start-time: "2023-12-12T00:00:00.000Z"
-             end-time: "2023-12-12T00:01:00.000Z"
-             interval: 5
-             allow-padding: true
-    ```
+  We have introduced the concept of global config to the plugins. This is truly global configuration data that should be kept constant regardless of where the plugin is invoked across the manifest file.
+
+  A good example is the `interpolation` method to use in the Teads curve plugin - this is not expected to vary from component to component and can therefore be defined in global config. The plugin code itself must expect the global config. Then, the config can be passed in the `Initialize` block, for example:
+
+  ```yaml
+  initialize:
+    plugins:
+      'time-sync':
+        method: TimeSync
+        path: 'builtin'
+        global-config:
+          start-time: '2023-12-12T00:00:00.000Z'
+          end-time: '2023-12-12T00:01:00.000Z'
+          interval: 5
+          allow-padding: true
+  ```
 
 - **Node level config**
 
-    We have also introduced the concept of node-level config. This is designed for pluin configuration that might vary between components in the tree. For example, for each child in the tree you might wish to use the `groupby` plugin to group the outputs according to a different set of keys.
+  We have also introduced the concept of node-level config. This is designed for pluin configuration that might vary between components in the tree. For example, for each child in the tree you might wish to use the `regroup` feature to group the outputs according to a different set of keys.
 
-    ```yaml
-    tree:
-      children:
-        child-1:
-          pipeline:
+  ```yaml
+  tree:
+    children:
+      child-1:
+        pipeline:
+          compute:
             - teads-curve
             - sci-e
             - sci-embodied
             - sci-o
             - time-sync
             - sci
-          config:
-            group-by:
-              group:
-                - region
-                - cloud/instance-type
-    ```
+          regroup:
+            - region
+            - cloud/instance-type
+  ```
 
 - **Defaults**
 
-    We have also introduced the concept of `defaults`. This is a section in each component's definition that can be used to provide fallbacks for missing input data. For example, perhaps you have a value arriving from an external API that should be present in every observation in your inputs array, but for soem reason the API fails to deliver a value for some timestamps. In this case, IF would fallback to the value provided for that metric in the `defaults` section of the manifest for that component.
+  We have also introduced the concept of `defaults`. This is a section in each component's definition that can be used to provide fallbacks for missing input data. For example, perhaps you have a value arriving from an external API that should be present in every observation in your inputs array, but for soem reason the API fails to deliver a value for some timestamps. In this case, IF would fallback to the value provided for that metric in the `defaults` section of the manifest for that component.
 
-    You can also use `defaults` as a quick way to add values to everyobservation in your input array if those values are expected to be constant over time (e.g. some of the lifespan values for embodied carbon calculations could be appropriate to include in defaults). This saves you from having to enter the value in every observation in the input array, instead IF can automatically grab it from `defaults` for every timestamp. 
+  You can also use `defaults` as a quick way to add values to everyobservation in your input array if those values are expected to be constant over time (e.g. some of the lifespan values for embodied carbon calculations could be appropriate to include in defaults). This saves you from having to enter the value in every observation in the input array, instead IF can automatically grab it from `defaults` for every timestamp.
 
-    ```yaml
-    tree:
-      children:
-        child-1:
-          pipeline:
+  ```yaml
+  tree:
+    children:
+      child-1:
+        pipeline:
+          compute:
             - teads-curve
             - sci-e
             - sci-embodied
             - sci-o
             - time-sync
             - sci
-         defaults:
-            cpu/thermal-design-power: 100
-            grid/carbon-intensity: 800
-            device/emissions-embodied: 1533.120 # gCO2eq
-            time-reserved: 3600 # 1hr in seconds
-            device/expected-lifespan: 94608000 # 3 years in seconds
-            resources-reserved: 1
-            resources-total: 8
-    ```
-
-
+       defaults:
+          cpu/thermal-design-power: 100
+          grid/carbon-intensity: 800
+          device/emissions-embodied: 1533.120 # gCO2eq
+          time-reserved: 3600 # 1hr in seconds
+          device/expected-lifespan: 94608000 # 3 years in seconds
+          resources-reserved: 1
+          resources-total: 8
+  ```
 
 ## New IF features
 
 ### Time-sync
-Technically time-sync is not a new feature as it was present in IF before the refactor, but there are some tweaks to how the plugin is configured that are worth explaining here. Time sync snaps all input arrays across an entire graph to a common time grid. 
+
+Technically time-sync is not a new feature as it was present in IF before the refactor, but there are some tweaks to how the plugin is configured that are worth explaining here. Time sync snaps all input arrays across an entire graph to a common time grid.
 
 This means you have to define a global start time, end time and interval to use everywhere. There is also a boolean to toggle whether you should allow the time sync model to pad the start and end of your time series with zeroes. You should default to `true` unless you have a specific reason not to. In the refactored IF we expect this information to be provided in global config, as follows:
 
 ```yaml
 initialize:
-    plugins:
-        "time-sync":
-          method: TimeSync
-          path: "builtin"
-          global-config:
-            start-time: "2023-12-12T00:00:00.000Z"
-            end-time: "2023-12-12T00:01:00.000Z"
-            interval: 5
-            allow-padding: true
+  plugins:
+    'time-sync':
+      method: TimeSync
+      path: 'builtin'
+      global-config:
+        start-time: '2023-12-12T00:00:00.000Z'
+        end-time: '2023-12-12T00:01:00.000Z'
+        interval: 5
+        allow-padding: true
 ```
 
 ### Aggregate
@@ -216,7 +199,7 @@ The aggregate plugin aggregates data in two ways: first it condenses individual
 
 This is a builtin feature of IF, meaning it does not have to be initialized as a plugin. Instead, you just have to include a short config block in the top of the manifest file. There are two pieces of information required:
 
-- `metrics`: which metrics do you want to aggregate? Every metric you provide here must exist in the output array. 
+- `metrics`: which metrics do you want to aggregate? Every metric you provide here must exist in the output array and be described in the `parameter-metadata` of the plugin.
 
 - `type`: the options are `horizontal`, `vertical` or both. Horizontal aggregation is the type that condenses each time series into a single summary value. Vertical aggregation is aggregated across components.
 
@@ -225,52 +208,16 @@ Here's what the config block should look like:
 ```yaml
 aggregation:
   metrics:
-    - 'carbon'
+    - carbon
   type: 'both'
 ```
 
-
-### Groupby
-
-Groupby allows you to regroup your outputs according to keys you define. For example, maybe you want to group your outputs by region (show me all the outputs for applications run in `uk-south` etc). Groupby *is* a plugin that needs to be initialized in the manifest.
-
-You can initialize the plugin as follows:
-
-```yaml
-initialize:
-  plugins:
-    'group-by':
-      path: builtin
-      method: GroupBy
-```
-
-Then you configure groupby for each component in the node level config. In the following example we will regroup the outputs by the `region`:
-
-```yaml
-tree:
-  children:
-    child-1:
-      pipeline:
-        - teads-curve
-        - sci-e
-        - sci-embodied
-        - sci-o
-        - time-sync
-        - group-by
-        - sci
-      config:
-        group-by:
-          group:
-            - region
-```
-
 ### Exhaust
 
-We have introduced `exhaust` as an IF feature. This is a wrapper around export plugins and it allows community contributors to create plugins for exporting to different formats. 
+We have introduced `exhaust` as an IF feature. This is a wrapper around export plugins and it allows community contributors to create plugins for exporting to different formats.
 
 Details tbc...
 
-
 ## Plugins
 
 The plugins themselves require some changes to keep them compatible with the refactored IF.
@@ -295,18 +242,17 @@ The plugin still requires an execute function. This is where you implement the p
 Here's a minimal example for a plugin that sums some inputs defined in global config - see inline comments for some important notes:
 
 ```ts
-
 // Here's the function definition - notice that global config is passed in here!
 export const Sum = (globalConfig: SumConfig): PluginInterface => {
   const inputParameters = globalConfig['input-parameters'] || [];
   const outputParameter = globalConfig['output-parameter'];
-    
-    // we also return metadata now too - you can add more or just use this default
+
+  // we also return metadata now too - you can add more or just use this default
   const metadata = {
     kind: 'execute',
   };
-    
-   /**
+
+  /**
    * Calculate the sum of the input metrics for each timestamp.
    */
   const execute = async (inputs: PluginParams[]): Promise<PluginParams[]> => {
@@ -332,7 +278,7 @@ export const Sum = (globalConfig: SumConfig): PluginInterface => {
     );
   };
 
-    // return the metadata and the execute function
+  // return the metadata and the execute function
   return {
     metadata,
     execute,

package/build/common/config/index.d.ts

@@ -0,0 +1 @@
+export { STRINGS } from './strings';

package/build/common/config/index.js

@@ -0,0 +1,6 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.STRINGS = void 0;
+var strings_1 = require("./strings");
+Object.defineProperty(exports, "STRINGS", { enumerable: true, get: function () { return strings_1.STRINGS; } });
+//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiaW5kZXguanMiLCJzb3VyY2VSb290IjoiIiwic291cmNlcyI6WyIuLi8uLi8uLi9zcmMvY29tbW9uL2NvbmZpZy9pbmRleC50cyJdLCJuYW1lcyI6W10sIm1hcHBpbmdzIjoiOzs7QUFBQSxxQ0FBa0M7QUFBMUIsa0dBQUEsT0FBTyxPQUFBIiwic291cmNlc0NvbnRlbnQiOlsiZXhwb3J0IHtTVFJJTkdTfSBmcm9tICcuL3N0cmluZ3MnO1xuIl19

package/build/common/config/strings.d.ts

@@ -0,0 +1,8 @@
+export declare const STRINGS: {
+    DISCLAIMER_MESSAGE: string;
+    SOURCE_IS_NOT_YAML: string;
+    TARGET_IS_NOT_YAML: string;
+    MANIFEST_NOT_FOUND: string;
+    SUCCESS_MESSAGE: string;
+    MANIFEST_IS_MISSING: string;
+};

package/build/common/config/strings.js

@@ -0,0 +1,16 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.STRINGS = void 0;
+exports.STRINGS = {
+    DISCLAIMER_MESSAGE: `
+Incubation Project
+
+This project is an incubation project being run inside the Green Software Foundation; as such, we DON’T recommend using it in any critical use case. 
+Incubation projects are experimental, offer no support guarantee, have minimal governance and process, and may be retired at any moment. This project may one day graduate, in which case this disclaimer will be removed.`,
+    SOURCE_IS_NOT_YAML: 'Given source file is not in yaml format.',
+    TARGET_IS_NOT_YAML: 'Given target file is not in yaml format.',
+    MANIFEST_NOT_FOUND: 'Manifest file not found.',
+    SUCCESS_MESSAGE: 'The environment is successfully setup!',
+    MANIFEST_IS_MISSING: 'Manifest is missing.',
+};
+//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoic3RyaW5ncy5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uLy4uL3NyYy9jb21tb24vY29uZmlnL3N0cmluZ3MudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7O0FBQWEsUUFBQSxPQUFPLEdBQUc7SUFDckIsa0JBQWtCLEVBQUU7Ozs7Mk5BSXFNO0lBQ3pOLGtCQUFrQixFQUFFLDBDQUEwQztJQUM5RCxrQkFBa0IsRUFBRSwwQ0FBMEM7SUFDOUQsa0JBQWtCLEVBQUUsMEJBQTBCO0lBQzlDLGVBQWUsRUFBRSx3Q0FBd0M7SUFDekQsbUJBQW1CLEVBQUUsc0JBQXNCO0NBQzVDLENBQUMiLCJzb3VyY2VzQ29udGVudCI6WyJleHBvcnQgY29uc3QgU1RSSU5HUyA9IHtcbiAgRElTQ0xBSU1FUl9NRVNTQUdFOiBgXG5JbmN1YmF0aW9uIFByb2plY3RcblxuVGhpcyBwcm9qZWN0IGlzIGFuIGluY3ViYXRpb24gcHJvamVjdCBiZWluZyBydW4gaW5zaWRlIHRoZSBHcmVlbiBTb2Z0d2FyZSBGb3VuZGF0aW9uOyBhcyBzdWNoLCB3ZSBET07igJlUIHJlY29tbWVuZCB1c2luZyBpdCBpbiBhbnkgY3JpdGljYWwgdXNlIGNhc2UuIFxuSW5jdWJhdGlvbiBwcm9qZWN0cyBhcmUgZXhwZXJpbWVudGFsLCBvZmZlciBubyBzdXBwb3J0IGd1YXJhbnRlZSwgaGF2ZSBtaW5pbWFsIGdvdmVybmFuY2UgYW5kIHByb2Nlc3MsIGFuZCBtYXkgYmUgcmV0aXJlZCBhdCBhbnkgbW9tZW50LiBUaGlzIHByb2plY3QgbWF5IG9uZSBkYXkgZ3JhZHVhdGUsIGluIHdoaWNoIGNhc2UgdGhpcyBkaXNjbGFpbWVyIHdpbGwgYmUgcmVtb3ZlZC5gLFxuICBTT1VSQ0VfSVNfTk9UX1lBTUw6ICdHaXZlbiBzb3VyY2UgZmlsZSBpcyBub3QgaW4geWFtbCBmb3JtYXQuJyxcbiAgVEFSR0VUX0lTX05PVF9ZQU1MOiAnR2l2ZW4gdGFyZ2V0IGZpbGUgaXMgbm90IGluIHlhbWwgZm9ybWF0LicsXG4gIE1BTklGRVNUX05PVF9GT1VORDogJ01hbmlmZXN0IGZpbGUgbm90IGZvdW5kLicsXG4gIFNVQ0NFU1NfTUVTU0FHRTogJ1RoZSBlbnZpcm9ubWVudCBpcyBzdWNjZXNzZnVsbHkgc2V0dXAhJyxcbiAgTUFOSUZFU1RfSVNfTUlTU0lORzogJ01hbmlmZXN0IGlzIG1pc3NpbmcuJyxcbn07XG4iXX0=

package/build/common/lib/load.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Parses manifest file as an object.
+ */
+export declare const load: (inputPath: string) => Promise<{
+    rawManifest: any;
+}>;

package/build/common/lib/load.js

@@ -0,0 +1,18 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.load = void 0;
+const yaml_1 = require("../util/yaml");
+const config_1 = require("../../if-run/config");
+const { LOADING_MANIFEST } = config_1.STRINGS;
+/**
+ * Parses manifest file as an object.
+ */
+const load = async (inputPath) => {
+    console.debug(LOADING_MANIFEST);
+    const rawManifest = await (0, yaml_1.openYamlFileAsObject)(inputPath);
+    return {
+        rawManifest,
+    };
+};
+exports.load = load;
+//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoibG9hZC5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uLy4uL3NyYy9jb21tb24vbGliL2xvYWQudHMiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6Ijs7O0FBQUEsdUNBQWtEO0FBRWxELGdEQUE0QztBQUU1QyxNQUFNLEVBQUMsZ0JBQWdCLEVBQUMsR0FBRyxnQkFBTyxDQUFDO0FBRW5DOztHQUVHO0FBQ0ksTUFBTSxJQUFJLEdBQUcsS0FBSyxFQUFFLFNBQWlCLEVBQUUsRUFBRTtJQUM5QyxPQUFPLENBQUMsS0FBSyxDQUFDLGdCQUFnQixDQUFDLENBQUM7SUFFaEMsTUFBTSxXQUFXLEdBQUcsTUFBTSxJQUFBLDJCQUFvQixFQUFNLFNBQVMsQ0FBQyxDQUFDO0lBRS9ELE9BQU87UUFDTCxXQUFXO0tBQ1osQ0FBQztBQUNKLENBQUMsQ0FBQztBQVJXLFFBQUEsSUFBSSxRQVFmIiwic291cmNlc0NvbnRlbnQiOlsiaW1wb3J0IHtvcGVuWWFtbEZpbGVBc09iamVjdH0gZnJvbSAnLi4vdXRpbC95YW1sJztcblxuaW1wb3J0IHtTVFJJTkdTfSBmcm9tICcuLi8uLi9pZi1ydW4vY29uZmlnJztcblxuY29uc3Qge0xPQURJTkdfTUFOSUZFU1R9ID0gU1RSSU5HUztcblxuLyoqXG4gKiBQYXJzZXMgbWFuaWZlc3QgZmlsZSBhcyBhbiBvYmplY3QuXG4gKi9cbmV4cG9ydCBjb25zdCBsb2FkID0gYXN5bmMgKGlucHV0UGF0aDogc3RyaW5nKSA9PiB7XG4gIGNvbnNvbGUuZGVidWcoTE9BRElOR19NQU5JRkVTVCk7XG5cbiAgY29uc3QgcmF3TWFuaWZlc3QgPSBhd2FpdCBvcGVuWWFtbEZpbGVBc09iamVjdDxhbnk+KGlucHV0UGF0aCk7XG5cbiAgcmV0dXJuIHtcbiAgICByYXdNYW5pZmVzdCxcbiAgfTtcbn07XG4iXX0=

package/build/{types → common/types}/manifest.d.ts

@@ -1,10 +1,13 @@
 import { z } from 'zod';
+import { AggregationMethodTypes } from '../../if-run/types/aggregation';
 import { manifestSchema } from '../util/validations';
 export type Manifest = z.infer<typeof manifestSchema>;
 export type GlobalPlugins = Manifest['initialize']['plugins'];
 export type PluginOptions = GlobalPlugins[string];
 export type AggregationParams = Manifest['aggregation'];
+export type AggregationMetricsWithMethod = {
+    [key: string]: AggregationMethodTypes;
+};
 export type AggregationParamsSure = Extract<Manifest['aggregation'], {}>;
 export type Context = Omit<Manifest, 'tree'>;
 export type ContextWithExec = Omit<Manifest, 'tree'>;
-export type ManifestParameter = Extract<Manifest['params'], {}>[number];

package/build/common/types/manifest.js

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