Danny

Can this be merged? Would very much like to use this 😄

The new capability is in the links in the first post, the added context to transform. The speedup is not 10% but the total overhead is now 10% (in our...

The first commit in this PR is indeed passing the context as extra arguments to the existing transform option, but that would break existing library users. (transform arity change) The...

If `o/insert` and `o/insert!` accepted functions as values (similar to `swap!`) then incremental updates would be possible by `conj` and `disj` the relationship, without first having to `query-all`

If `:then-finally` means on-retract in your fork, does the README example use with `query-all` still work? Or how would you write that? We use it heavily to build up little...

Incremental updates is definitely something I'd want. What I mean though is the derived facts example that collects once in `:then-finally` and in our case inserts that set into the...

Thanks. In our case odoyle runs over an event log, to decide what actual side effects to do next: insert log into session, fire rules, query next actions. Running the...

Action as in side-effect: network calls. Nothing to do with odoyle. We use odoyle as a pure function. Some rules need to be aware if the API calls have already...

I was actually thinking about doing a little experiment implementing a [Network layer](https://relay.dev/docs/guides/network-layer/) `fetchQuery` that doesn't really fetch over HTTP, but gets data from local SQLite. It would do this...

With a generic entity schema it will be easy to know which Node IDs are invalid, but is there currently a way to invalidate only the active queries currently rendering...