.NET event sourcing library with CosmosDB, DynamoDB, EventStoreDB, message-db, SqlStreamStore and integration test backends. Focused at stream level; see https://github.com/jet/propulsion for cross-stream projections/subscriptions/reactions
*StoreContext keeps its name, even though it would be nice if the name alluded to or referenced the facts that:
it selects a target subspace in what the *StoreClient can hit (database+container, table, schema, etc), which suggest a role name such as Target or Config
it owns the tip options/batch options/query options, which represent the bulk of configuration, which suggest the role name *Config
'context on *StoreContext should be entitled 'req, with instances named req (probably same in FsCodec?)
(not relevant in this repo much; mainly in dotnet-templates) Store.Context should be renamed Store.Config, with instances named store
Context on ITimelineEvent can stay named as it is, I guess (it could be called Tag ?
*StoreContext
keeps its name, even though it would be nice if the name alluded to or referenced the facts that:*StoreClient
can hit (database+container, table, schema, etc), which suggest a role name such as Target or Config'context
on*StoreContext
should be entitled'req
, with instances namedreq
(probably same in FsCodec?)dotnet-templates
)Store.Context
should be renamedStore.Config
, with instances namedstore
Context
onITimelineEvent
can stay named as it is, I guess (it could be calledTag
?cc @mydogisbox @nordfjord