Fork me on GitHub
#boot
<
2018-07-06
>
alexyakushev15:07:19

@richiardiandrea

alexyakushev15:07:56

[edn] or [sym] used to be treated as accumulated arguments (that you can specify multiple times), now that only works for sets. Not sure if that's the desired behavior, but in any case, there are still plenty of tasks that have such arguments.

alexyakushev15:07:56

Also, even if that's intended, this is a breaking change for anyone with custom tasks that relied on this syntax.

richiardiandrea15:07:25

Uhm yes this seems different now - we could revert but it will break the pom with parent feature, I will have a look later today

richiardiandrea15:07:29

Probably a buggy implementation ...no tests were around that oops

alandipert15:07:02

thanks @alexyakushev for tracking that down

richiardiandrea15:07:15

Thanks definitely

alexyakushev15:07:30

Perhaps, some other notation is needed for this SYM:VER=PATH thing. Something more explicit.

alexyakushev15:07:48

a parent SYM:VER=PATH (sym str str)? 🙂 Seems like lists haven't yet been used.

alexyakushev15:07:13

Or something like #tuple[sym str str]

richiardiandrea15:07:18

Can there be nested lists in a parameter list? Because I could flatten in case we have one only

alexyakushev17:07:32

What if you want e.g. a list of SYM:VER=PATH?