Max

Results 5 comments of Max

+1 to the explicit `before` and `after` in this proposal. I've seen instances where ambiguous execution order of `orchestrator`s vs `mutator`s leads to subtle bugs and hard to maintain code...

I'd be interested in getting in on something like this as well. Mind linking it in the comments once you've created the repo?

The simplest solve for this is to move to a package structure like this ``` package ├── test │ └── fence.json │ └── ...tests ├── lib │ └── fence.json ```...

Should we consider migrating to [wasm-git](https://github.com/petersalomonsen/wasm-git) instead?

It is, I would need to keep partial reconstructions of the tree stored in memory and then rebuild from a single node changing