Open
Conversation
ReneFerrari
force-pushed
the
cold-controller-support
branch
from
bba4257 to
a214e40
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
1 participant
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.
Allows for creation of a Cold Controller.
Why is it called SubscriptionAwareController and not ColdController? I initially had ColdController but the issue is that SharingStarted could be used in a way that allows for a Hot Controller - by using SharingStarted.Eagerly.
I'm obviously open for name suggestions.
Currently tests are missing.
What I also don't like at the moment is that in both subclasses i had to define a companion object with all funs / the const from the base class. Maybe somebody has a solution here.