graphula
graphula copied to clipboard
freckle
A simple interface for generating persistent data and linking its dependencies
I hit these errors but because they don't give useful info, they were kind of a dead-end. Gonna dogfood this at work before marking it as ready for review. I...
I think the answer is no. I ran into this error: ``` /home/cody/smurf/test/ITProTV/Database/Particle/Models/HostSpec.hs:49:27-51: error: • Couldn't match type ‘Database.MongoDB.Query.MongoContext’ with ‘Database.Persist.Sql.Types.Internal.SqlBackend’ arising from a use of ‘node’ • In a...
Replay via `seed` is extremely useful for determining if a circumstance is flakiness or intrinsic. Non `HUnit` exceptions are not caught by `graphula` so unexpected IO exceptions cannot be replayed....
Currently `Insert` returns `Maybe a`. `Nothing` is coded for constraint failure, which triggers retry. If retry fails we throw a generation error. This error is opaque and does not provide...
On failure an idempotent graph should be able to shrink results to produce the smallest failure case possible. There are a lot of variables here. Should every value be shrunken...
Without being able to refer to `EntityKeys`, if one defines a polymorphic function that makes use of `keys`, it is not possible to express the type signature.
`ensure` can be wasteful, it may generate many values before the condition is met. We currently use it often to ensure a field is `Just`: ```hs ... $ ensure $...
