ci: update angular-cli (minor) #269
Merged
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:
0.1002.0
->0.1100.1
10.2.3
->11.0.0
10.2.7
->11.0.0
10.2.0
->11.0.1
10.2.3
->11.0.0
10.2.3
->11.0.0
10.2.3
->11.0.0
10.2.3
->11.0.0
10.2.3
->11.0.0
10.2.3
->11.0.0
10.2.7
->11.0.0
10.2.3
->11.0.0
10.2.3
->11.0.0
10.2.3
->11.0.0
Release Notes
angular/angular
v11.0.0
Compare Source
Bug Fixes
OnPush
component when inputs change (#39452) (dd28855), closes /github.com/angular/angular/blob/3236ae0ee118d0734c90fa9f3767435396213470/packages/upgrade/src/common/src/downgrade_component_adapter.ts#L146 #38948r
->Y
(#39495) (feda78e)fullTemplateTypeCheck
is disabled (#39320) (67ea7b6), closes #38195ngDevMode
is undeclared (#39415) (cc32932)LView
rather than inTView
(#39233) (0992b67), closes #37021 #38144 #38073ngDevMode
for undefined. (#36055) (f541e5f)KeyValuePipe
(#37447) (4dfe0fa)SlicePipe
(#37447) (4744c22)null
(#36259) (#37447) (c7d5555)params
andreportProgress
options toHttpClient.put()
overload (#37873) (dd8d8c8), closes #23600let
statements in ES2015+ mode (#38775) (123bff7)DatePipe
(#38009) (26f2820), closes /www.ecma-international.org/ecma-262/5.1/#sec-15 #37989statusChanges
on subsequent value update/validations (#38354) (d9fea85), closes #20424 #14542Features
relativeLinkResolution
migration to update default value (#38698) (15ea811)TemplateTypeChecker
operation to getSymbol
from a template node (#38618) (c4556db)Symbol
ofTemplate
s andElement
s in component template (#38618) (cf2e8b9)Symbol
of AST expression in component template (#38618) (f56ece4)UnrecoverableStateError
(#36847) (036a2fa), closes #36539Performance Improvements
ngDevMode
to tree-shake error messages in router (#38674) (db21c4f)BREAKING CHANGES
useAbsoluteUrl
to setupplatform-server
, you now need toalso specify
baseUrl
.We are intentionally making this a breaking change in a minor release,
because if
useAbsoluteUrl
is set totrue
then the behavior of theapplication could be unpredictable, resulting in issues that are hard to
discover but could be affecting production environments.
initialNavigation
property for the options inRouterModule.forRoot
no longer supportslegacy_disabled
,legacy_enabled
,true
, orfalse
as valid values.legacy_enabled
(the old default) is insteadenabledNonBlocking
enabled
is deprecated as a valid value for theRouterModule.forRoot
initialNavigation
option.enabledBlocking
has been introduced to replace it
queryParamsHandling="preserve" instead
RouterLink
values ofqueryParams
,fragment
orqueryParamsHandling
you might need to relax the typing to alsoaccept
undefined
andnull
. (#39151)ViewEncapsulation.Native
has been removed. UseViewEncapsulation.ShadowDom
instead. Existingusages will be updated automatically by
ng update
.in Ivy. This may cause compilation failures if errors are found in
expressions that appear within an ICU. Please correct these expressions
to resolve the type-check errors.
@angular/forms
package used to haveany[]
as a type ofvalidators
andasyncValidators
arguments in constructors. Now these arguments are properly typed, so if yourcode relies on directive constructor types it may require some updates to improve type safety.
null
is now included in the types of .parent. If you don't already have a check for this case,the TypeScript compiler might complain. A v11 migration exists which adds the non-null assertion
operator where necessary. In an unlikely case your code was testing the parent against undefined with strict equality,
you'll need to change this to
=== null
instead, since the parent is now explicitly initializedwith
null
instead of being leftundefined
.10, and IE mobile support completely.
Supporting outdated browsers like these increases bundle size, code complexity, and test load,
and also requires time and effort that could be spent on improvements to the framework.
For example, fixing issues can be more difficult, as a straightforward fix for modern browsers
could break old ones that have quirks due to not receiving updates from vendors.
have been removed as they were deprecated in v8
slice
pipe now returnsnull
for theundefined
input value,which is consistent with the behavior of most pipes. If you rely on
undefined
being the result in that case, you now need to check for itexplicitly.
keyvalue
pipe has been fixed to report that forinput objects that have
number
keys, the result will contain thestring representation of the keys. This was already the case and the
code has simply been updated to reflect this. Please update the
consumers of the pipe output if they were relying on the incorrect
types. Note that this does not affect use cases where the input values
are
Map
s, so if you need to preservenumber
s, this is an effectiveway.
accepted. This should only cause issues in corner cases, as any other
values would result in runtime exceptions.
date
pipe now explicitly states which types areaccepted. This should only cause issues in corner cases, as any other
values would result in runtime exceptions.
undefined
for an input thatwas typed as
undefined
. Note that the code actually returnednull
onundefined
inputs. In the unlikely case you were relying on this,please fix the typing of the consumers of the pipe output.
map both
null
andundefined
tonull
and raise an exception oninvalid input (
0
,false
,NaN
) just like most "common pipes". Ifyour code required falsy values to pass through, you need to handle them
explicitly.
NavigationExtras
to be passed in, they will not allow object literals,as they may only specify known properties. They will also not accept
types that do not have properties in common with the ones in the
Pick
.To fix this error, only specify properties from the
NavigationExtras
which areactually used in the respective function calls or use a type assertion
on the object or variable:
as NavigationExtras
.relativeLinkResolution
from'legacy'
to'default'
. If yourapplication previously used the default by not specifying a value in the
ExtraOptions
and uses relative links when navigating from children ofempty path routes, you will need to update your
RouterModule
tospecifically specify
'legacy'
forrelativeLinkResolution
.See https://angular.io/api/router/ExtraOptions#relativeLinkResolution
for more details.
TestBed.overrideProvider
after TestBed initialization, provider overrides are not applied. Thisbehavior is consistent with other override methods (such as
TestBed.overrideDirective
, etc) but theythrow an error to indicate that, when the check was missing in the
TestBed.overrideProvider
function.Now calling
TestBed.overrideProvider
after TestBed initialization also triggers anerror, thus there is a chance that some tests (where
TestBed.overrideProvider
iscalled after TestBed initialization) will start to fail and require updates to move
TestBed.overrideProvider
callsbefore TestBed initialization is completed.
RouteReuseStrategy#shouldReuseRoute. Previously, when evaluating child
routes, they would be called with the future and current arguments would
be swapped. If your RouteReuseStrategy relies specifically on only the future
or current snapshot state, you may need to update the shouldReuseRoute
implementation's use of "future" and "current" ActivateRouteSnapshots.
than mutable arrays, since these arrays are shared across calls to the
API. If you were mutating them (e.g. calling
sort()
,push()
,splice()
, etc)then your code will not longer compile. If you need to mutate the array, you
should now take a copy (e.g. by calling
slice()
) and mutate the copy.DatePipe
in a format that containsfractions of a millisecond, the milliseconds will now always be rounded down rather than
to the nearest millisecond. Most applications will not be affected by this change. If this is not the desired behaviour
then consider pre-processing the string to round the millisecond part before passing
it to the
DatePipe
.defined at initialization time, the status change event was not emitted once async validator
completed. After this change the status event is emitted into the
statusChanges
observable.If your code relies on the old behavior, you can filter/ignore this additional status change
event.
Code Refactoring
10.2.3 (2020-11-09)
Bug Fixes
10.2.2 (2020-11-04)
Bug Fixes
fullTemplateTypeCheck
is disabled (#39320) (71d0063), closes #38195Performance Improvements
10.2.1 (2020-10-28)
Bug Fixes
ngDevMode
is undeclared (#39415) (fcebc83)angular/components
v11.0.0
Compare Source
cdk
material
Breaking changes:
rather than the alert and status roles.
@angular/material/core
have beenremoved. These have been accidentally published in the past while they
were only intended for internal consumption in tests.
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled due to failing status checks.
♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.