Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Can't bind ObservableType to BehaviorRelay #1466
Short description of the issue:
It's not possible to bind ObservableType to BehaviorRelay as it was possible to bind ObservableType to Variable.
Since BehaviorRelay is considered a replacement for Variable, it should offer a hassle free migration. ObservableType should know how to bind itself to BehaviorRelay since that's the intention of
Self contained code example that reproduces the issue:
//This doesn't compile Observable.just(false).bind(to: BehaviorRelay(value: true)) //This still compiles Observable.just(false).bind(to: Variable(true))
How easy is to reproduce? (chances of successful reproduce after running the self contained code)
referenced this issue
Oct 23, 2017
@dakeshi We've for now only put
We haven't marked it deprecated right now because I'm assuming people will have hard time migrating to 4.0 APIs, and unfortunately I'm assuming that there is a lot of
We wanted to help people for now by just informing them about the deprecation. It is possible we'll move
That would enable newcomers to find relays more easily and we would have some consistency with behavior and publish relays.
We still haven't decided how exactly we'll deprecate
When the exact deprecation path is decided, we'll potentially add deprecation warnings if that API will be removed completely or in case of
@kzaher Thanks for your detailed response.
What I feel strange is
And how do developers or new comers know
I can't think of a better way of informing people some API will be deprecated than adding it to a file named
When migration path is decided it will get it's