Andrey Nering

@ghostsquad Once you're done to write a few examples of what you have in mind, that would certainly be interesting. 🙂

Hi @d3dc, I'm not sure what is the most expected behavior here. I think hearing opinions from more users would be nice before changing. In the meantime, you can use...

Hi @shilangyu, thanks for opening this issue! This doesn't work because it was not originally intended to work like this. It may makes sense to respect that, though...

Anybody is free to comment here about what you expect for v4. The community feedback was always taken into account in the project. 🙂 Some things are still missing, and...

@ghostsquad It's not that breaking changes are disallowed, but I want to avoid them unless necessary. For example, I noticed [you renamed some attributes](https://github.com/ghostsquad/task/blob/feat/v4/sdk/v4/taskfile/task.go) on your PoC branch (`cmds` became...

@ghostsquad Changing a bit the subject... can you describe how to you see the lazy variables working? Maybe a couple of simple examples? I'm curious to see what is coming....

I still don't think we should rename attributes without a good reason. These are the suggestions from the [PoC branch](https://github.com/ghostsquad/task/blob/feat/v4/sdk/v4/taskfile/task.go): - `deps` -> `needs_of` (or `needs`?) - `desc` -> `short`...

Hi @max-sixty , I think that having a task attribute to validate that given vars are required probably makes sense 👍.

Hi @tylermmorton, > Personally I feel like there could be some performance implications with running setup commands before every single command in a task. I'm open to suggestions/feedback from the...

Hi @Yottum, I think this just isn't supported by https://github.com/mattn/go-zglob. Can you check if you glob use cases work on [Gosh](https://github.com/mvdan/sh)? You can do that by installing Gosh and running:...