Empty defaults?

[broarr]

Hey all,

I'm trying to learn more about how if works. I found this behavior that I found surprising. If I leave out the defaults key, if-run fails. If I keep defaults empty, if-run also fails. If I define any default, even one that is unrelated to my pipeline if succeeds. Is that intended? Below are two minimal examples of manifests that break. If it's not intended can I submit a PR for it?

name: absent default
description: example manifest to error with missing defaults
tags:
initialize:
  plugins:
    divide:
      path: "builtin"
      method: Divide
      config:
        numerator: "test1"
        denominator: "test2"
        output: "test3"

tree:
  children:
    job:
      pipeline:
        observe:
        regroup:
        compute:
          - divide
        inputs:
          - test1: 32.694612
            test2: 32.327209

name: empty default
description: example manifest to error with empty defaults
tags:
initialize:
  plugins:
    divide:
      path: "builtin"
      method: Divide
      config:
        numerator: "test1"
        denominator: "test2"
        output: "test3"

tree:
  children:
    job:
      defaults:
      pipeline:
        observe:
        regroup:
        compute:
          - divide
        inputs:
          - test1: 32.694612
            test2: 32.327209

This is the error that I keep getting

[2025-02-04 04:20:52.499 PM] info: 	
Graduated Project

This project is a Graduated Project, supported by the Green Software Foundation. The publicly available version documented in the README is trusted by the GSF. New versions of the project may be released, or it may move to the Maintained or Retired Stage at any moment.

INFO: 2025-02-04T21:20:52.501Z: Starting IF
DEBUG: 2025-02-04T21:20:52.501Z: Loading manifest
DEBUG: 2025-02-04T21:20:52.503Z: Capturing runtime environment data
DEBUG: 2025-02-04T21:20:52.774Z: Validating manifest
DEBUG: 2025-02-04T21:20:52.776Z: Initializing plugins,

DEBUG: 2025-02-04T21:20:52.776Z: Initializing `divide` instance
DEBUG: 2025-02-04T21:20:52.776Z: Loading Divide from builtin,

**Computing `job` pipeline**
DEBUG: 2025-02-04T21:20:52.804Z: Merging defaults with input data,


DEBUG: 2025-02-04T21:20:52.804Z: Running compute pipeline: `divide` plugin
[2025-02-04 04:20:52.805 PM] TypeError: 	Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at Object.execute (/Users/broarr/src/s12y-dscov-sci/node_modules/@grnsft/if-core/interfaces/index.js:90:34)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async computeNode (/Users/broarr/src/s12y-dscov-sci/node_modules/@grnsft/if/build/if-run/lib/compute.js:144:29)
    at async traverse (/Users/broarr/src/s12y-dscov-sci/node_modules/@grnsft/if/build/if-run/lib/compute.js:19:9)


DEBUG: 2025-02-04T21:20:52.805Z: divide: Preparing output data,

# start
name: empty default
description: example manifest to error with empty defaults
tags: null
initialize:
  plugins:
    divide:
      path: builtin
      method: Divide
      config:
        numerator: test1
        denominator: test2
        output: test3
execution:
  status: fail
  command: >-
    /Users/broarr/.local/share/mise/installs/node/22.13.0/bin/node
    /Users/broarr/src/s12y-dscov-sci/node_modules/.bin/if-run -m minimal.yml
    --debug
  environment:
    if-version: 1.0.0
    os: macOS
    os-version: '15.2'
    node-version: 22.13.0
    date-time: 2025-02-04T21:20:52.772Z (UTC)
    dependencies:
      - '@grnsft/[email protected]'
  error: 'TypeError: Cannot convert undefined or null to object'
tree:
  children:
    job:
      defaults: null
      pipeline:
        observe: null
        regroup: null
        compute:
          - divide
        inputs:
          - test1: 32.694612
            test2: 32.327209

# end
INFO: 2025-02-04T21:20:52.806Z: divide: Exiting IF

[broarr]

I tried to repro this today and could not. Turns out that I indented inputs one too many times