Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Illustrate do proposal. #869

Closed
wants to merge 1 commit into from

Conversation

fjtirado
Copy link
Collaborator

@fjtirado fjtirado commented May 30, 2024

Just opened this one in the context of a slack discussion. Its not intended to be merged or reviewed and will be closed once we end the discussion.
This will allow writing (in main flow, loops and retries)
Either unnamed single tasks (this assumes singles tasks can be univocally referenced through json pointers, which I believe is a valid one)

do:
   set:

on named multiple tasks (multiple tasks needs to be named to be reference univocally)

do: 
  task1: 
    set:
do:
  task2: 
    call: http

This will prevent writing

do:
  set: 
    set: 

which is valid now for main flow (it defines a task named set which invoke set tasks)

@fjtirado fjtirado force-pushed the do_proposal branch 2 times, most recently from e00bda8 to c3788e2 Compare May 30, 2024 19:57
@matthias-pichler
Copy link
Collaborator

Is this event still relevant with #875 ?

@fjtirado
Copy link
Collaborator Author

fjtirado commented Jun 3, 2024

@matthias-pichler-warrify Partially , because whatever the do: schema finally is, in my opinion, it should be the same both for main flow, loop and retries. I mean, if we allow sequential execution of task for main flow though do: list of task, in loops and retries we should allow a list of tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants