Bismarck dependency graph

[asarazan]

Need a way for a bismarck to "depend" on another bismarck, such that changes cascade down the dependency graph.

Should be pretty straightforward. It's probably just a clever use of eachValue

[treelzebub]

is this closed now that we have RescopedBismarck?

[asarazan]

No I don't think so. This is about how if the account list was invalidated then your transaction list probably needs a refetch.

Iirc rescoped was more about coroutine semantics

[treelzebub]

Right right. The pattern of taking a bismarck in the constructor and delegating by parent could be abstracted out, then consumers could override/call super as they please.

[asarazan]

Actually not quite. This is literally just calling bismarck.dependsOn(someOtherBismarck).

Example:

transactionsBismarck.dependsOn(accountsBismarck) // now our invalidate calls will cascade

[treelzebub]

i see i see. do we think dependsOn adequately conveys invalidation dependency? as this is a destructive relationship, should we call it out more plainly?

[asarazan]

Good question! If the idea is that bismarck doesn't require much babysitting and just invalidates/updates you according to its own internal logic, then this is a good extension of that.

However I definitely held off including it in v1 because it's super confusing, and also a potential source of bugs. It was objectively helpful at preventing stale data bugs back in the level days though.