Make tasks names optional

[JBBianchi]

As the result of #875, the idea of having named properties to describe tasks, such as:

document:
   #...
do: 
   task1:
      call: http
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task1
   task2:
      call: http
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task2
   task3:
      call: http
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task3

has been dropped because neither JSON not YAML have guaranteed properties ordering. The workflow above could be parsed with the property task3 before task2. With implicit then, it would result in the unwanted execution of task3 before task2.

Therefore, to insure the ordering of the tasks, we'll have to rely on an array instead. For instance (in accordance with #872 and #884):

document:
   #...
do: 
  sequentially :
    - task1:
        call: http
        with:
          endpoint: 
            uri: https://fake-endpoint.com/task1
    - task2:
        call: http
        with:
          endpoint: 
            uri: https://fake-endpoint.com/task2
    - task3:
        call: http
        with:
          endpoint: 
            uri: https://fake-endpoint.com/task3

This raises again another point already mentioned by #869 which is to leave names optional and have something like this instead:

document:
   #...
do: 
  sequentially :
    - call: http
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task1
    - call: http
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task2
    - call: http
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task3

If more flow control is needed, names can be provided:

document:
   #...
do: 
  sequentially :
    - switch:
        case1:
          when: .foo == "foo"
          then: task1
        case1:
          when: .foo == "bar"
          then: task2
      then: task3
    - call: http
      name: task1
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task1
    - call: http
      name: task2
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task2
    - call: http
      name: task3
      with:
        endpoint: 
          uri: https://fake-endpoint.com/task3

What's your take @cdavernas @fjtirado @matthias-pichler-warrify @ricardozanini ?

[cdavernas]

We already reached a consensus to go with:

do:
  - myTaskName:
      call: ...

Like Google Workflows.

Your second proposal is the same than not having names. If they are optional, noone will use them, ever. Also, it hinders fluency imo.

[JBBianchi]

Ok, nvm, there were 24 hidden messages I didn't see. If a consensus was reached then we can close this discussion.

[fjtirado]

@JBBianchi I prefer the second approach (name as optional, in fact I proposed that here) , but @cdavernas prefer the first one and I do not want to press the issue, so Im willing to compromise.
Just for historical record ;), I believe is better to put the name in the task object because that way you can name the task no matter if the task is single or multi, up to the user.
But again, this, in my opinion, is a question of opinion ;)