Replies: 1 comment
-
Hi @neerfri, glad to hear you are enjoying it! The closest we have to this is branching sections but they certainly won't give everything you need and I think that, even if we improve support for this, I think you would sooner rather than later run into another blocker. I think the execution graph should likely be decoupled from Livebook execution model (or to be more precise, Livebooks cannot represent an arbitrary execution graph right now and perhaps never will). Maybe we will revisit it in the future, but certainly out of scope for now. :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Love livebook! It's awesome!! 🙏
I was wondering if there were any thoughts regarding a more complex control flow of a notebook execution path than a list.
For example, Imagine a notebook that implements a deploy script.
If the application is already deployed the steps are different than those of an upgrade, so the notebook author wishes to (and automate) both versions in one notebook.
Of course this simple case can be done with a simple elixir
if
, that's not the intent here, the intent is to visually show the execution-path in the notebook UI that was chosen and skip the "disabled" cells.Another use case, if we stick to the same use-case, is to deploy to multiple locations and have a visual representation of an execution path that is traversing in parallel.
In my mind I see something like hierarchical cells, for example:
Or:
Any thoughts?
Thanks ✌️
Beta Was this translation helpful? Give feedback.
All reactions