Elijah ben Izzy

We have decided to do this, just for function-based actions

This is complete

> Hello. Please assign it to me @Dipec001 assigned! Going to respond in a minute with directions on what to do

Hey @Dipec001! Some guidance here (responding as well to the discord note you left, sorry it's been a busy day): 1. Familiarize yourself with the [example of the counter app](https://github.com/DAGWorks-Inc/burr/tree/253a03d972b912bb95b25a92c8137f7988696807/examples/hello-world-counter)...

This is very likely dependent on #33 -- we'll need to layer/apply updates to state in a nice way. We can probably get around that but it is worth considering.

> What I would do today is just do it internal to the action: > > > > ```python > > @action(...) > > def my_parallel_action(state: State, .. ) ->...

Plan of action: Use-case (sample, for scrapegraph): - [ ] List a bunch of URLs - [ ] Run a single step that spawns multiple graphs - [ ] Join...

Design for phase (1): ```python @action(...) def spawning_action(..., __context: AppContext): app = ( ApplicationBuilder()... .with_spawning_parent( __context.app_id, __context.sequence_id) .with_tracker(__context.tracker) .build() ) ... = app.run(...) return ... ```

Looking at the second phase here -- how do we make this ergonomic? We'll need an action to specify: 1. How to map — E.G. generate subgraphs/actions from state —...

Some raw notes from a chat with @skrawcz yesterday: ```python with_actions( parallel_example=MapReduceAction( lambda state: [ TaskSpec(...) for item in state["item_to_map_over"] ] ) ) # this is self-contained @action(reads=[], writes=[]) def...