Billy Mumby
Billy Mumby
**Is your feature request related to a problem? Please describe.** It would be really great if the library could offer an opt-int repository that would allow a document to be...
Given you are using the in-memory repository implementation and you make use of the new types `IWriteOnlyRepository` and `IReadOnlyRepository` if you resolve them both for the same `TItem` then say...
If we fail to handle a change from the change feed. We want to make sure that we store a copy of that event. We can write this `EventItem` directly...
We can make use of another container or maybe an in-memory cache to guarantee that an event won't be processed more than once. This would use the unique ID of...
It might be the case that events might need to be archived and then removed after a period of time. ```csharp public class ArchivableEventItem : EventItem { public bool IsArchived...
The file that contains all of the in-memory implementations is getting quite large. It would be great to see this tidied up a little. See the work that was done...
We have recently introduced paging into the `DefaultRepository` but there is not yet support for the continuation token version in the `InMemoryRepository`. This could return a `Guid` as the token...
It would be really nice if we could look at an extensions package of some sort maybe along the lines of `Microsoft.Azure.CosmosEventSourcing.Extensions.AzureServiceBus`. This could contain a way to define a...
Some docs on the change feed support ahead of the release: - [x] How to configure the change feed for a specific item type - [ ] Explain you can...