You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generate compatible state change events when testing hydrate
This is unfortunately very "white-boxy" and the testing code needs to
know that the generated events must be using parameters consistent with
the environment.
The alternative would be to move checkHeadState outside of hydrate, but
then 'WetHydraNode's can exist without this check happening.
--| Analogous to inputs, the pure head logic "core" can have effects emited to
22
23
-- the "shell" layers and we distinguish the same: effects onto the client, the
@@ -105,14 +106,37 @@ instance HasEventId (StateChanged tx) where
105
106
-- FIXME(Elaine): these stateChangeID fields were added in an attempt to make every StateChanged keep track of its ID
106
107
-- it's not clear how to handle the state for this. but for now the field is kept so that the type of putEvent can be kept simple, and shouldn't do harm
107
108
108
-
instance (IsTxtx, Arbitrary (HeadStatetx), Arbitrary (ChainStateTypetx)) =>Arbitrary (StateChangedtx) where
0 commit comments