-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RXWAIT observable$.cache is not a function #108
Comments
I can fix this, if Im able to do a pull |
Please consider this change as your next RC |
Any workaround for this? |
get the operator/cache.(js|d.ts|map) file from "rxjs": "5.0.0-beta.12" and add to your app or to node_modules/rxjs/operator/ & node_modules/rxjs/add/operator/ |
RXWAIT is not really working properly even with |
I used Console shows: How to resolve this problem? Its necessary to change node_modules folder? |
Create a file with this content export function cache(
} export interface CacheSignature { at some main location in your app `import { cache, CacheSignature } from '../services/cache'; Observable.prototype.cache = cache; declare module 'rxjs/Observable' { |
This is somewhat of a blocker, I think ReactiveX/rxjs#2443 |
this issue is in beta.10 milestone.. but rc was released after bata.9 ? |
I tried to fix this in core but this is not possible, the rxjs typings/imports are needed to get this working. I think the At the moment I doubt anyone is using So I propose @christopherthielen What do you think, is this possible? Edit: I think the correct place to implement |
Am I missing something or is this not a pretty major showstopper for an Angular 2+ router? Observables are all over the place in Angular now. Is the suggested workaround just to "toPromise" everything? |
Also, its been around for nearly a year, can we take RXWAIT out of the docs? |
Got the same error in my project: Solved it by promisifying all my Observables... |
DEC 2018 still no workaround ? |
.cache is deprecated now. We should change this to .share() or publish().refCount(1)
The text was updated successfully, but these errors were encountered: