feat(EventStoreDb): Add AccessStrategy.CustomOrigin#222
Draft
feat(EventStoreDb): Add AccessStrategy.CustomOrigin#222
Conversation
cd5febc to
e92891c
Compare
22cfdd4 to
644aaa2
Compare
Collaborator
Author
|
See also #263 - similar considerations make me not want to expose it until someone has a use case that we can't provide a clean workaround for |
b1a5694 to
a7486eb
Compare
1919c31 to
b7e2207
Compare
fe2af41 to
edda98d
Compare
7053335 to
07a8d79
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Provides a
Equinox.EventStore.AccessStrategy.CustomOriginwhich would be useful in the context of jet/dotnet-templates#40 to enable a custom lookback on a long-running stream (without employing the snapshots strategy).🤔 Still mulling over whether this is truly a good idea to expose in Equinox