Skip to content

docs: use static zip function as an Observable creator. - #26790

Closed
ajcrites wants to merge 1 commit into
angular:masterfrom
ajcrites:backoff-zip-example
Closed

ajcrites wants to merge 1 commit into
angular:masterfrom
ajcrites:backoff-zip-example

Conversation

@ajcrites

Copy link
Copy Markdown

The existing example makes it seem like zip is a pipeable operator. It can be used this way, but I think that is for backwards compatibility. You can achieve the same functionality by using it as an Observable creator. I think this also makes the example clearer.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

Does this PR introduce a breaking change?

  • Yes
  • No

@ajcrites
ajcrites force-pushed the backoff-zip-example branch from 9fa8ba1 to 1418b54 Compare October 26, 2018 20:27
@brandonroberts brandonroberts added comp: docs action: review The PR is still awaiting reviews from at least one requested reviewer effort2: days refactoring Issue that involves refactoring or code-cleanup area: router target: patch This PR is targeted for the next patch release state: community Someone from the Angular community is working on this issue or submitted this PR labels Oct 29, 2018
@ngbot ngbot Bot added this to the needsTriage milestone Oct 29, 2018
@brandonroberts brandonroberts self-assigned this Oct 29, 2018
@ngbot ngbot Bot modified the milestones: needsTriage, Backlog Oct 30, 2018
@benlesh benlesh added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 8, 2019
@benlesh

benlesh commented Jan 8, 2019

Copy link
Copy Markdown
Contributor

Nice! Thanks @ajcrites!

The existing example makes it seem like zip is a pipeable operator. It can be used this way, but I think that is for backwards compatibility. You can achieve the same functionality by using it as an Observable creator. I think this also makes the example clearer.
@kara
kara force-pushed the backoff-zip-example branch from 1418b54 to 4a1f42d Compare January 9, 2019 00:13
@ajcrites
ajcrites requested a review from a team January 9, 2019 00:13
@kara
kara removed the request for review from a team January 9, 2019 00:13
@kara

kara commented Jan 9, 2019 •

Copy link
Copy Markdown
Contributor

@ajcrites FYI, rebased this because our CI checks weren't triggered properly (ancient bug that has since been fixed)

kara pushed a commit that referenced this pull request Jan 9, 2019
The existing example makes it seem like zip is a pipeable operator. It can be used this way, but I think that is for backwards compatibility. You can achieve the same functionality by using it as an Observable creator. I think this also makes the example clearer.

PR Close #26790
@kara kara closed this in 1de4031 Jan 9, 2019
AndrewKushnir pushed a commit that referenced this pull request Jan 16, 2019
The existing example makes it seem like zip is a pipeable operator. It can be used this way, but I think that is for backwards compatibility. You can achieve the same functionality by using it as an Observable creator. I think this also makes the example clearer.

PR Close #26790
@angular-automatic-lock-bot

Copy link
Copy Markdown

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 14, 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 area: router cla: yes effort2: days refactoring Issue that involves refactoring or code-cleanup risk: low state: community Someone from the Angular community is working on this issue or submitted this PR target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants