Confusion around 'Conduit' terminology #16
Description
The name of the product "Conduit" is confusingly similar to the Haskell terminology of Data.Conduit. And to further complicate this, the conduit package is actually used in the backend as well.
But this is a source of confusion, it is not clear what role does the conduit package play and in the code where do we refer to which?
I don't have a solution, but a suggestion is to add a note explaining it a little more.
From my guess the conduit package is used just in Backend.Conduit.Database to perhaps stream the db requests and responses. And the Conduit everywhere else is just the product name.