yaml support

[MrSmiler]

What do you think about adding yaml support beside toml, what would be the problems ?
One problem i can think is that we can't embed the yaml to pyproject.toml file, so have to include it.
With yaml we can write better nested and complex structures and most ci/cd platforms and even other task runners use this syntax.
This is an example how poe would be in yaml:

build:
  help: build the product
  control_expr: sys.platform
    - case: win32
      sequence: 
        - shell: "echo Building on windows with version: ${version}"
          interpreter: powershell
        - ref: .package      
    - case: linux
      sequence: 
        - shell: "echo Building on linux with version: ${version}"
          interpreter: bash
        - ref: .package
  args:
    - name: version
      options: 
        - -v
        - --version
      help: product version
      required: true

.package:
  help: package the product binary
  cmd: echo Compress product binary file

[nat-n]

Hi @MrSmiler,

I thought about this a while ago for included task files but IIRC I was put off by the idea of adding another dependency. Thinking about it again now having a dependency on pyyaml with lazy importing doesn't seem like too big a deal. So yea, why not?

I've also been thinking it would be nice to support having root task files other than pyproject.toml, so maybe just working with something like tasks.yaml in a project that doesn't have poetry would be nice, though I haven't fully thought through how this would work.

[MrSmiler]

That's great to hear.
So at the end we would support two configuration syntax, one problem would that any feature you think to implement, it should be supported in both syntax which makes double the effort and test, but instead we provide more options for our users to use our tool and we get more users and attention, would you be ok with this ?
If yes then where do we should begin ? would like me to make proof of concept code about just portion of current features in yaml to see what happens ?

[nat-n]

The way I see it there are two distinct features here.

1. adding support for running tasks without a pyproject.toml. This is a bit more complex and requires more thought about exactly how it should work.
2. supporting yaml task files with include, just like how json files are already supported. This would be quite simple to implement around here. I would be happy to review a PR for this.

I don't think either feature really requires changing the structure of the config.

[MrSmiler]

Oh ok, it look easy.
I will try to go for it.

[nat-n]

FYI, I started working on this feature myself.

[MrSmiler]

thank you and sorry I could not make time for helping you on this.

[nat-n]

@MrSmiler As of v0.29.0 you can now declare tasks in a poe_tasks.(toml|json|yaml) file as an alternative to pyproject.toml, and you can include tasks from yaml files.

[MrSmiler]

really appreciate