CLI: cannot checkout a project spec.yaml directly

[josephjclark]

If I have a project spec (exported from lightning in the new portability spec), and I try to do openfn checkout project.yaml, I get this error:

[CLI] ✘ Command failed!
[CLI] ✘ TypeError: Cannot convert undefined or null to object
    at Object.values (<anonymous>)
    at mapWorkflow2 (file:///home/joe/repo/openfn/kit/packages/project/dist/index.js:834:10)
    at file:///home/joe/repo/openfn/kit/packages/project/dist/index.js:800:12
    at Array.map (<anonymous>)
    at from_app_state_default (file:///home/joe/repo/openfn/kit/packages/project/dist/index.js:799:55)
    at from_v1 (file:///home/joe/repo/openfn/kit/packages/project/dist/index.js:915:10)
    at from_project_default (file:///home/joe/repo/openfn/kit/packages/project/dist/index.js:912:10)
    at from_path_default (file:///home/joe/repo/openfn/kit/packages/project/dist/index.js:935:10)
    at async handler3 (file:///home/joe/repo/openfn/kit/packages/cli/dist/process/runner.js:3527:21)
    at async parse (file:///home/joe/repo/openfn/kit/packages/cli/dist/process/runner.js:4179:12)

Skimming over the code it looks like we're expecting to import from a state v1 file, with { triggers, steps, edges }. I'm not sure why that would be - we should be way smarter about identifying the format we're parsing.

I suspect that when checking out a yaml file directly, I've hard-coded it to be a v1 import

[josephjclark]

Ok, I see it

We call fs.from('path'), which in turn calls Project.from('project', data). And that defaults to loading v1 format unless certain keys are set in the yaml.

So the issue really is: when loading a project from a yaml file, be a bit better at working out which format we should be using