Use pipeable operators instead of imperative imports

[mgol]

There are places (like this one in http-client-backend.service.ts) where this module uses the old-style RxJS imperative imports. They should be switched to the new pipeable operators that don't rely on side-effects.

I've discovered this in my app where removing in-memory-web-api made some modules suddenly fail due to missing map & filter methods on observables.

[mgol]

Correction - it's actually the imports from rxjs/add that are adding these methods to the prototype:

in-memory-web-api/src/app/http-client-hero.service.ts

Lines 7 to 9 in f7e216d

	import 'rxjs/add/operator/do';
	import 'rxjs/add/operator/catch';
	import 'rxjs/add/operator/map';

[wardbell]

You are looking at the sample app, not the library. The library does NOT import 'rxjs/add/operator';; let me know if you find where it does.

This library is supposed to work with the old RxJS method chaining as well as the newer pipeable operators. The sample app still reflects the old approach. But this shouldn't affect your user-land code at all. When you include this library in your application, you should not find that those methods have been added to prototypes in YOUR code.

I'll leave this open a few days so you can contradict me. I'd need to see a repro.

Thanks.
W

[mgol]

I'm sorry, you're right; it was another package that was importing from 'rxjs/add/operator' in my project.