-
Notifications
You must be signed in to change notification settings - Fork 26.2k
docs: ensure examples get rxjs ^5.5.0 #19985
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
You can preview 9a8f049 at https://pr19985-9a8f049.ngbuilds.io/. |
This updates all dependencies, not just RxJS. If that is intentional, it should be reflected in the commit message. |
@gkalpak Huh? Only for samples. All sample are already governed by Oh ... I see. You mean it will update versions of other packages in package.json that were implied but not installed because existing I'll be more explicit in the main comment. Also updated the commit message accordingly |
This change coincidentally updates other packages that were in `package.json` because it regenerates `yarn.lock`. This too should be fine.
9a8f049
to
fca0ed1
Compare
You can preview fca0ed1 at https://pr19985-fca0ed1.ngbuilds.io/. |
This change coincidentally updates other packages that were in `package.json` because it regenerates `yarn.lock`. This too should be fine. PR Close #19985
Should have been companion to PR angular#19985
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. |
URGENT - please merge ASAP as we have very little time to update docs before next NG release.
Added patch label as well; RxJS v.5.5 is backward compat for Ng v4
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
All doc samples get there
node_modules
from one place,.../aio/tools/shared/examples/package.json
.This
package.json
and itsyarn.lock
are currently pinned to RxJS <5.5 so we can't show or explain the RxJS features that we should now be recommending to everyone.In user land, people using the CLI are getting 5.5.x today.
Issue Number: #19510 concerning upgrading Docs for v5 Angular and latest CLI
What is the new behavior?
Installs latest RxJS >= 5.5.0
Although the focus is strictly RxJS, the regenerated yarn.lock updates all other package dependencies currently specified in
package.json
.That is unintentional but probably a good thing as we should be consistent.
If something goes wrong with this, we will fix it.
Does this PR introduce a breaking change?