-
Notifications
You must be signed in to change notification settings - Fork 0
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
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/angular-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bffd3bf
to
0a4e4b2
Compare
44fb0cb
to
1739798
Compare
5dad0c8
to
c601ca6
Compare
c601ca6
to
0f01e75
Compare
0f01e75
to
0e56c30
Compare
0e56c30
to
4a26262
Compare
4a26262
to
a39a363
Compare
a39a363
to
359bb00
Compare
359bb00
to
7d9dcb9
Compare
7d9dcb9
to
94dadce
Compare
94dadce
to
6705636
Compare
6705636
to
a2343db
Compare
a2343db
to
163fe28
Compare
163fe28
to
f46216a
Compare
f46216a
to
c6e6e24
Compare
c6e6e24
to
2651e55
Compare
2651e55
to
0b90e5e
Compare
f3046a9
to
de8f7ee
Compare
de8f7ee
to
940a34b
Compare
b8455c9
to
3154a25
Compare
3154a25
to
7f7fdb0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.4.5
->2.4.10
2.4.5
->2.4.10
2.4.5
->2.4.10
2.4.5
->2.4.10
2.4.5
->2.4.10
2.4.5
->2.4.10
2.4.5
->2.4.10
3.4.5
->3.4.10
0.2.4
->0.17.0
0.7.6
->0.14.3
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
v0.10.0
Compare Source
v0.9.0
Compare Source
v0.8.0
Compare Source
@angular/http
supportBREAKING CHANGE
This version no longer supports any functionality for
@angular/http
. Please use@angular/common/http
instead.v0.7.0
Compare Source
v0.6.1
Compare Source
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 usesinterval()
).Also fixes type error (issue #180).
v0.5.3
Compare Source
Can make use of
HttpParams
which yields arequest.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 fromfalse
totrue
. 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 mappingthe HTTP response results from the
data
property like this:To migrate, simply remove that line everywhere.
If you would rather keep the web api's encapsulation,
{data: ...}
, setdataEncapsulation
totrue
during configuration as in the following example:We made this change because
Almost everyone seems to hate the encapsulation
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 forHttpClient
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 learningHttpClient
itself.Now you just write
http.get<Hero[]>()
and you’ve got data (please add error handling).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.
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.
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
v0.4.5
Compare Source
Feature - offer separate
HttpClientInMemoryWebApiModule
andHttpInMemoryWebApiModule
.closes #140
v0.4.4
Compare Source
closes #136
A breaking change if you expected
genId
to generate ids for a collectionwith 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 theget
,delete
,post
, orput
methods.replace all
switchMap
withconcatMap
because, in all previous uses ofswitchMap
,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 theRequestInfo
interface and set it inhandleRequest_
get
,delete
,post
, andput
methods get thecollection
fromrequestInfo
; 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
Http
andHttpClient
to intercept Angular's attempt to call browser's XHR
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.
HttpClient
-> renaming of backend service classesPOST commands/resetDb
passes the request to yourresetDb
methodso you can optionally reset the database dynamically
to arbitrary initial states (issue #128)
geniD
RequestInfo.utils
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
forHttpModule
and thetslib
package.To see how, look in the
map
section of thesrc/systemjs.config.js
for this project for the following two additional lines :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 runnpm 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
v0.3.1
Compare Source
See PR #102.
v0.3.0
Compare Source
v0.2.5
Compare Source
angular/angular (zone.js)
v0.14.3
Compare Source
Bug Fixes
Features
v0.14.2
Compare Source
Bug Fixes
v0.14.1
Compare Source
v0.14.0
Compare Source
Features
BREAKING CHANGES
dist/
imports likezone.js/bundles/zone-testing.js
andzone.js/dist/zone
are no longer allowed.zone-testing-bundle
andzone-testing-node-bundle
are also no longer part of the package.The proper way to import
zone.js
andzone.js/testing
is:0.13.3 (2023-09-12)
Bug Fixes
typings
conditional export totypes
(#51737) (74755c4)0.13.2 (2023-09-07)
Bug Fixes
v0.13.1 (2023-06-09)
Bug Fixes
queueMicrotask()
API in node.js (#50467) (381cb98)queueMicrotask()
API in node.js (#50530) (7837f71)Features
Reverts
queueMicrotask()
API in node.js (#50467)" (#50529) (7567348), closes #50467 #50529 #50529v0.13.3
Compare Source
Bug Fixes
typings
conditional export totypes
(#51737) (74755c4)v0.13.2
Compare Source
Bug Fixes
v0.13.1
Compare Source
Bug Fixes
queueMicrotask()
API in node.js (#50467) (381cb98)queueMicrotask()
API in node.js (#50530) (7837f71)Features
Reverts
queueMicrotask()
API in node.js (#50467)" (#50529) (7567348), closes #50467 #50529 #50529v0.13.0
Compare Source
v0.12.0
Compare Source
Bug Fixes
0.11.8 (2022-08-08)
Features
0.11.7 (2022-07-20)
Bug Fixes
waitForAsync
(4e77c7fbf38)Features
describe
block name when raising unexpected task error (de86285)0.11.6 (2022-06-02)
Bug Fixes
process
is defined when patching theGlobalErrors.install
(#45392) (c7bcc1b), closes #42260Symbol.species
safely (#45369) (e2eaac3)BREAKING CHANGES
The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking
. If you usedTaskTrackingZoneSpec
andchecked the pending macroTasks e.g. using
(this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask')
, thenits behavior slightly changed for periodic macrotasks. For example,
previously the
setInterval
macrotask was no longer tracked after itscallback 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
done()
multiple times (#45025) (d5565cc)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
Build
BREAKING CHANGES
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
v0.11.7
Compare Source
Bug Fixes
waitForAsync
(4e77c7fbf38)Features
describe
block name when raising unexpected task error (de86285)v0.11.6
Compare Source
Bug Fixes
process
is defined when patching theGlobalErrors.install
(#45392) (c7bcc1b), closes #42260Symbol.species
safely (#45369) (e2eaac3)BREAKING CHANGES
The breaking change is scoped only to the plugin
zone.js/plugins/task-tracking
. If you usedTaskTrackingZoneSpec
andchecked the pending macroTasks e.g. using
(this.ngZone as any)._inner ._parent._properties.TaskTrackingZone.getTasksFor('macroTask')
, thenits behavior slightly changed for periodic macrotasks. For example,
previously the
setInterval
macrotask was no longer tracked after itscallback 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.
This PR has been generated by Mend Renovate. View repository job log here.