Skip to content

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

Merged
merged 1 commit into from
Oct 31, 2017

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Oct 31, 2017

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.

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.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 31, 2017
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Oct 31, 2017
@andrewseguin
Copy link
Contributor

LGTM - thanks for doing all the work

CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Oct 31, 2017
* Removes 'rxjs/operators' import in favor of indivial imports,
  adds lint rule to prevent that type of import
* Maintains parity with angular/components#8160
@andrewseguin andrewseguin added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Oct 31, 2017
@andrewseguin andrewseguin merged commit de8c6e2 into angular:master Oct 31, 2017
@seangwright
Copy link

@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!

CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Nov 7, 2017
* Removes 'rxjs/operators' import in favor of indivial imports,
  adds lint rule to prevent that type of import
* Maintains parity with angular/components#8160
CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Nov 7, 2017
* Removes 'rxjs/operators' import in favor of indivial imports,
  adds lint rule to prevent that type of import
* Maintains parity with angular/components#8160
CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Nov 24, 2017
* Removes 'rxjs/operators' import in favor of indivial imports,
  adds lint rule to prevent that type of import
* Maintains parity with angular/components#8160
CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Nov 24, 2017
* Removes 'rxjs/operators' import in favor of indivial imports,
  adds lint rule to prevent that type of import
* Maintains parity with angular/components#8160
CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Nov 24, 2017
* Removes 'rxjs/operators' import in favor of indivial imports,
  adds lint rule to prevent that type of import
* Maintains parity with angular/components#8160
CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Nov 25, 2017
* Removes 'rxjs/operators' import in favor of indivial imports,
  adds lint rule to prevent that type of import
* Maintains parity with angular/components#8160
@danwulff
Copy link

danwulff commented Dec 1, 2017

@crisbeto @jelbourn. Could you take a look at @sgwatgit 's question. I'm also curious about this change, especially as a maintainer of an angular library.

CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Dec 7, 2017
* 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
CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Dec 14, 2017
* 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
CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Dec 14, 2017
* 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
CaerusKaru added a commit to CaerusKaru/flex-layout that referenced this pull request Dec 14, 2017
* 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
ThomasBurleson pushed a commit to angular/flex-layout that referenced this pull request Dec 14, 2017
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.
atscott pushed a commit to atscott/flex-layout that referenced this pull request Feb 3, 2018
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.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants