Skip to content
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

fix(deps): update angular monorepo #32

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 17, 2018

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular/common (source) 2.4.5 -> 2.4.10 age adoption passing confidence
@angular/compiler (source) 2.4.5 -> 2.4.10 age adoption passing confidence
@angular/compiler-cli (source) 2.4.5 -> 2.4.10 age adoption passing confidence
@angular/forms (source) 2.4.5 -> 2.4.10 age adoption passing confidence
@angular/http 2.4.5 -> 2.4.10 age adoption passing confidence
@angular/platform-browser (source) 2.4.5 -> 2.4.10 age adoption passing confidence
@angular/platform-browser-dynamic (source) 2.4.5 -> 2.4.10 age adoption passing confidence
@angular/router (source) 3.4.5 -> 3.4.10 age adoption passing confidence
angular-in-memory-web-api (source) 0.2.4 -> 0.17.0 age adoption passing confidence
zone.js (source, changelog) 0.7.6 -> 0.14.3 age adoption passing confidence

Release Notes

angular/angular (@​angular/common)

v2.4.10

Compare Source

v2.4.9

Compare Source

v2.4.8

Compare Source

v2.4.7

Compare Source

v2.4.6

Compare Source

angular/angular (@​angular/compiler)

v2.4.10

Compare Source

v2.4.9

Compare Source

v2.4.8

Compare Source

v2.4.7

Compare Source

v2.4.6

Compare Source

angular/angular (@​angular/compiler-cli)

v2.4.10

Compare Source

v2.4.9

Compare Source

v2.4.8

Compare Source

v2.4.7

Compare Source

v2.4.6

Compare Source

angular/angular (@​angular/forms)

v2.4.10

Compare Source

v2.4.9

Compare Source

v2.4.8

Compare Source

v2.4.7

Compare Source

v2.4.6

Compare Source

angular/angular (@​angular/http)

v2.4.10

Compare Source

v2.4.9

Compare Source

v2.4.8

Compare Source

v2.4.7

Compare Source

v2.4.6

Compare Source

angular/angular (@​angular/platform-browser)

v2.4.10

Compare Source

v2.4.9

Compare Source

v2.4.8

Compare Source

v2.4.7

Compare Source

v2.4.6

Compare Source

angular/angular (@​angular/platform-browser-dynamic)

v2.4.10

Compare Source

v2.4.9

Compare Source

v2.4.8

Compare Source

v2.4.7

Compare Source

v2.4.6

Compare Source

angular/angular (angular-in-memory-web-api)

v0.17.0

Compare Source

v0.16.0

Compare Source

v0.15.0

Compare Source

v0.14.0

Compare Source

v0.11.0

Compare Source

  • update to support Angular v10.
  • no functional changes.

v0.10.0

Compare Source

v0.9.0

Compare Source

  • update to support Angular version 8.x and forward
  • no functional changes

v0.8.0

Compare Source

  • remove @angular/http support
  • no functional changes

BREAKING CHANGE
This version no longer supports any functionality for @angular/http. Please use
@angular/common/http instead.

v0.7.0

Compare Source

  • update to support Angular v7.
  • no functional changes

v0.6.1

Compare Source

  • update to Angular and RxJS v6 releases

v0.6.0

Compare Source

Migrate to Angular v6 and RxJS v6 (rc and beta)

Note that this release is pinned to Angular "^6.0.0-rc.0" and RxJS "^6.0.0-beta.1".
Will likely update again when they are official.

BREAKING CHANGE
This version depends on RxJS v6 and is not backward compatible with earlier RxJS versions.

v0.5.4

Compare Source

Simulated HTTP error responses were not delaying the prescribed time when using RxJS delay()
because it was short-circuited by the ErrorResponse.
New delayResponse function does it right.
Should not break you unless you incorrectly expected no delay for errors.

Also, this library no longer calls RxJS delay() which may make testing with it easier
(Angular TestBed does not handle RxJS delay() well because that operator uses interval()).

Also fixes type error (issue #​180).

v0.5.3

Compare Source

Can make use of HttpParams which yields a request.urlWithParams.
Added supporting HeroService.searchHeroes(term: string) and test.

v0.5.2

Compare Source

No longer modify the request data coming from client. Fixes #​164

v0.5.1

Compare Source

Support Angular v5.

v0.5.0

Compare Source

BREAKING CHANGE: HTTP response data no longer wrapped in object w/ data property by default.

In this release, the dataEncapsulation configuration default changed from false to true. The HTTP response body holds the data values directly rather than an object that encapsulates those values, {data: ...}. This is a breaking change that affects almost all existing apps!

Changing the default to false is a breaking change. Pre-existing apps that did not set this property explicitly will be broken because they expect encapsulation and are probably mapping
the HTTP response results from the data property like this:

  .map(data => data.data as Hero[])

To migrate, simply remove that line everywhere.

If you would rather keep the web api's encapsulation, {data: ...}, set dataEncapsulation to true during configuration as in the following example:

HttpClientInMemoryWebApiModule.forRoot(HeroInMemDataService, { dataEncapsulation: true })

We made this change because

  1. Almost everyone seems to hate the encapsulation

  2. Encapsulation requires mapping to get the desired data out. With old Http that isn't too bad because you needed to map to get data anyway (res => res.json()). But it is really ugly for HttpClient because you can't use the type HTTP method type parameter (e.g., get<entity-type>) and you have to map out of the data property (.map(data => data.data as Hero[]). That extra step requires explanations that distract from learning HttpClient itself.
    Now you just write http.get<Hero[]>() and you’ve got data (please add error handling).

  3. While you could have turned off encapsulation with configuration as of v.0.4, to do so took yet another step that you’d have to discover and explain. A big reason for the in-mem web api is to make it easy to introduce and demonstrate HTTP operations in Angular. The out-of-box experience is more important than avoiding a breaking change.

  4. The security flaw
    that prompted encapsulation seems to have been mitigated by all (almost all?) the browsers that can run an Angular (v2+) app. We don’t think it’s needed anymore.

  5. A most real world APIs today will not encapsulate; they’ll return the data in the body without extra ceremony.

v0.4.6

Compare Source

  • improves README
  • updates v0.4.0 entry in the CHANGELOG to describe essential additions to SystemJS configuration.
  • no important functional changes.

v0.4.5

Compare Source

Feature - offer separate HttpClientInMemoryWebApiModule and HttpInMemoryWebApiModule.

closes #​140

v0.4.4

Compare Source

closes #​136

A breaking change if you expected genId to generate ids for a collection
with non-numeric item.id.

v0.4.3

Compare Source

Refactoring for clarity and to correctly reflect intent.
A breaking change only if your customizations depend directly and explicitly on RequestInfo or the get, delete, post, or put methods.

  • replace all switchMap with concatMap because, in all previous uses of switchMap,
    I really meant to wait for the source observable to complete before beginning the inner observable whereas switchMap starts the inner observable right away.

  • restored collection to the RequestInfo interface and set it in handleRequest_

  • get, delete, post, and put methods get the collection from requestInfo; simplifies their signatures to one parameter.

v0.4.2

Compare Source

  • Postpones the in-memory database initialization (via resetDb) until the first HTTP request.

  • Your createDb method can be asynchronous.
    You may return the database object (synchronous), an observable of it, or a promise of it. Issue #​113.

  • fixed some rare race conditions.

v0.4.1

Compare Source

Support PassThru.

The passthru feature was broken by 0.4.0

  • add passthru to both Http and HttpClient
  • test passThru feature with jasmine-ajax mock-ajax plugin
    to intercept Angular's attempt to call browser's XHR
  • update devDependency packages
  • update karma.conf with jasmine-ajax plugin

v0.4.0

Compare Source

Theme: Support HttpClient and add tests.
See PR #​130.

The 0.4.0 release was a major overhaul of this library.

You don't have to change your existing application code if your app uses this library without customizations.

But this release's breaking changes affect developers who used the customization features or loaded application files with SystemJS.

BREAKING CHANGES: Massive refactoring.
Many low-level and customization options have changed.
Apps that stuck with defaults should be (mostly) OK.

If you're loading application files with SystemJS (as you would in a plunker), see the instructions below.

  • added support for HttpClient -> renaming of backend service classes
  • added tests
  • refactor existing code to support tests
  • correct bugs and clarify choices as result of test
  • add some configuration options
  • POST commands/resetDb passes the request to your resetDb method
    so you can optionally reset the database dynamically
    to arbitrary initial states (issue #​128)
  • when HTTP method interceptor returns null/undefined, continue with service's default processing (pr #​120)
  • can substitute your own id generator, geniD
  • parseUrl -> parseRequestUrl
  • utility methods exposed in RequestInfo.utils
  • reorganize files into src/app and src/in-mem
  • adjust gulp tasks accordingly

Plunkers and SystemJS

If you’re loading application files with SystemJS (as you would in a plunker), you’ll have to configure it to load Angular’s umd.js for HttpModule and the tslib package.

To see how, look in the map section of the
src/systemjs.config.js for this project for the following two additional lines :

'@&#8203;angular/common/http': 'npm:@&#8203;angular/common/bundles/common-http.umd.js',
...
'tslib': 'npm:tslib/tslib.js',

You've already made these changes if you are using HttpClient today.

If you’re sticking with the original Angular Http module, you must make this change anyway! Your app will break as soon as you run npm install and it installs >=v0.4.0.

If you're using webpack (as CLI devs do), you don't have to worry about this stuff because webpack bundles the dependencies for you.


v0.3.2

Compare Source

  • Bug fixes PRs #​91, 95, 106

v0.3.1

Compare Source

  • Now runs in node so can use in "universal" demos.
    See PR #​102.

v0.3.0

Compare Source

  • Support Angular version 4

v0.2.5

Compare Source

angular/angular (zone.js)

v0.14.3

Compare Source

Bug Fixes
Features

v0.14.2

Compare Source

Bug Fixes
  • zone.js: disable wrapping unhandled promise error by default (6d7eb35)

v0.14.1

Compare Source

v0.14.0

Compare Source

Features
BREAKING CHANGES
  • zone.js: Deep and legacy dist/ imports like zone.js/bundles/zone-testing.js and zone.js/dist/zone are no longer allowed. zone-testing-bundle and zone-testing-node-bundle are also no longer part of the package.

The proper way to import zone.js and zone.js/testing is:

import 'zone.js';
import 'zone.js/testing';

0.13.3 (2023-09-12)

Bug Fixes

0.13.2 (2023-09-07)

Bug Fixes

v0.13.1 (2023-06-09)

Bug Fixes
Features
Reverts

v0.13.3

Compare Source

Bug Fixes

v0.13.2

Compare Source

Bug Fixes

v0.13.1

Compare Source

Bug Fixes
Features
Reverts

v0.13.0

Compare Source

v0.12.0

Compare Source

Bug Fixes

0.11.8 (2022-08-08)

Features
  • zone.js: Update to the simpler Async Stack Tagging v2 API (#​46958) (f23232f)

0.11.7 (2022-07-20)

Bug Fixes
  • zone.js: do not invoke jasmine done callback multiple times with waitForAsync (4e77c7fbf38)
Features
  • zone.js: add AsyncStackTaggingZoneSpec implementation (#​46693) (848a009)
  • zone.js: include jasmine describe block name when raising unexpected task error (de86285)
  • zone.js: include zone name when sync-test zone reports tasks (72c2567)

0.11.6 (2022-06-02)

Bug Fixes
BREAKING CHANGES
  • zone.js: in TaskTrackingZoneSpec track a periodic task until it is cancelled

The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you used TaskTrackingZoneSpec and
checked the pending macroTasks e.g. using (this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), then
its behavior slightly changed for periodic macrotasks. For example,
previously the setInterval macrotask was no longer tracked after its
callback was executed for the first time. Now it's tracked until
the task is explicitly cancelled, e.g with clearInterval(id).

0.11.5 (2022-03-03)

Bug Fixes
Features

0.11.4 (2021-02-10)

Bug Fixes
Features

0.11.3 (2020-10-27)

Bug Fixes

0.11.2 (2020-09-19)

Bug Fixes
Features
Refactor
  • zone.js: refactor(zone.js): rename several internal apis in fake async zone spec (#​39127) (8a68669)
Build
  • zone.js: build(zone.js): zone.js should output esm format for fesm2015 bundles (#​39203) (822b838)
BREAKING CHANGES
  • zone.js: ZoneJS no longer swallows errors produced by Object.defineProperty calls.

Prior to this change, ZoneJS monkey patched Object.defineProperty and if there is an error
(such as the property is not configurable or not writable) the patched logic swallowed it
and only console.log was produced. This behavior used to hide real errors,
so the logic is now updated to trigger original errors (if any). One exception
where the patch remains in place is document.registerElement
(to allow smooth transition for code/polyfills that rely on old behavior in legacy browsers).
If your code relies on the old behavior (where errors were not thrown before),
you may need to update the logic to handle the errors that are no longer masked by ZoneJS patch.

0.11.1 (2020-08-19)

Bug Fixes

v0.11.8

Compare Source

Features
  • zone.js: Update to the simpler Async Stack Tagging v2 API (#​46958) (f23232f)

v0.11.7

Compare Source

Bug Fixes
  • zone.js: do not invoke jasmine done callback multiple times with waitForAsync (4e77c7fbf38)
Features
  • zone.js: add AsyncStackTaggingZoneSpec implementation (#​46693) (848a009)
  • zone.js: include jasmine describe block name when raising unexpected task error (de86285)
  • zone.js: include zone name when sync-test zone reports tasks (72c2567)

v0.11.6

Compare Source

Bug Fixes
BREAKING CHANGES
  • zone.js: in TaskTrackingZoneSpec track a periodic task until it is cancelled

The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking. If you used TaskTrackingZoneSpec and
checked the pending macroTasks e.g. using (this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask'), then
its behavior slightly changed for periodic macrotasks. For example,
previously the setInterval macrotask was no longer tracked after its
callback was executed for the first time. Now it's tracked until
the task is explicitly cancelled, e.g with clearInterval(id).

v0.11.5

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/angular-monorepo branch from bffd3bf to 0a4e4b2 Compare July 25, 2018 23:42
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 5 times, most recently from 44fb0cb to 1739798 Compare August 8, 2018 21:48
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 4 times, most recently from 5dad0c8 to c601ca6 Compare August 22, 2018 22:37
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from c601ca6 to 0f01e75 Compare August 27, 2018 04:56
@renovate renovate bot changed the title chore(deps): update angular monorepo to v6 chore(deps): update angular monorepo Aug 27, 2018
@renovate renovate bot changed the title chore(deps): update angular monorepo fix(deps): update angular monorepo Sep 4, 2018
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 0f01e75 to 0e56c30 Compare August 10, 2019 08:58
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 0e56c30 to 4a26262 Compare August 20, 2019 04:56
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 4a26262 to a39a363 Compare May 2, 2020 23:00
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from a39a363 to 359bb00 Compare August 21, 2020 00:00
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 359bb00 to 7d9dcb9 Compare October 28, 2020 16:57
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 7d9dcb9 to 94dadce Compare November 27, 2020 13:57
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 94dadce to 6705636 Compare April 26, 2021 13:36
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 6705636 to a2343db Compare March 7, 2022 13:40
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from a2343db to 163fe28 Compare June 18, 2022 21:42
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from f46216a to c6e6e24 Compare March 16, 2023 15:31
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from c6e6e24 to 2651e55 Compare May 28, 2023 09:12
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 2651e55 to 0b90e5e Compare June 12, 2023 18:17
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 3 times, most recently from f3046a9 to de8f7ee Compare September 18, 2023 10:37
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from de8f7ee to 940a34b Compare October 26, 2023 18:07
@renovate renovate bot force-pushed the renovate/angular-monorepo branch 2 times, most recently from b8455c9 to 3154a25 Compare November 8, 2023 19:56
@renovate renovate bot force-pushed the renovate/angular-monorepo branch from 3154a25 to 7f7fdb0 Compare January 9, 2024 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
0 participants