-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix: import individual rx operators #8160
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
Conversation
After the switch to lettable operators, we had started importing all operators via `rxjs/operators`. These changes switch us back to only importing the individual ones and add some linting so it doesn't happen in the future.
LGTM - thanks for doing all the work |
* Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
@crisbeto After reading about the option to us lettable operators in the ng 5 annoucement blog I was wondering why the ng Material team has chosen to use the deep lettable operators compared to the ones mentioned in the blog or in the rxjs repo docs . Does the approach you've chosen work better at scale, does it cause fewer issues with build systems or is it to support older versions of Typescript? Just curious! Thanks! |
* Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* fix: import individual rx operators * Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* fix: import individual rx operators * Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* fix: import individual rx operators * Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
* fix: import individual rx operators * Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160
Updates rxjs to latest best practices * fix: import individual rx operators * Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160 Fixes #519, #508, #533. Closes #474.
Updates rxjs to latest best practices * fix: import individual rx operators * Removes 'rxjs/operators' import in favor of indivial imports, adds lint rule to prevent that type of import * Maintains parity with angular/components#8160 Fixes angular#519, angular#508, angular#533. Closes angular#474.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
After the switch to lettable operators, we had started importing all operators via
rxjs/operators
. These changes switch us back to only importing the individual ones and adds some linting so it doesn't happen in the future.