Now that we have a better idea about exactly what kind of subgraph state transitions we need, we can remove unneeded transition logic from SubgraphStateTracker. State retention across refreshes is thrown away in favor of a simpler interface Result<Option<T>, E>, akin to SubgraphApi.
Also including a new unit test which tests the GlobalState deserialization logic.
@tilacog welcoming feedback before merging this, if you have any.
neysofu
commented
1 year ago
Now that we have a better idea about exactly what kind of subgraph state transitions we need, we can remove unneeded transition logic from
SubgraphStateTracker. State retention across refreshes is thrown away in favor of a simpler interfaceResult<Option<T>, E>, akin toSubgraphApi.Also including a new unit test which tests the
GlobalStatedeserialization logic.@tilacog welcoming feedback before merging this, if you have any.