build: update angular packages #18946
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:
8472c9e->9bbc3ad11.0.0-next.3->11.0.0-next.458b384c->8d32055784d1df->9735c8011.0.0-next.3->11.0.0-next.41983c5a->ada005b11.0.0-next.3->11.0.0-next.4bebf4f9->c62197311.0.0-next.3->11.0.0-next.4a867fcf->f53349411.0.0-next.3->11.0.0-next.4e82a9d3->166f11011.0.0-next.3->11.0.0-next.456f1c42->575074e22fd8c5->e9479c911.0.0-next.3->11.0.0-next.46acc2c5->e98cd9cfcbb86b->cb7ca35b5b32ae->bf1a7c711.0.0-next.3->11.0.0-next.45cd115f->b94005a11.0.0-next.3->11.0.0-next.4781005e->be8211d11.0.0-next.3->11.0.0-next.49644935->ec201de11.0.0-next.3->11.0.0-next.411.0.0-next.3->11.0.0-next.4🔡 If you wish to disable git hash updates, add
":disableDigestUpdates"to the extends array in your config.Release Notes
angular/angular
v11.0.0-next.4Compare Source
Bug Fixes
KeyValuePipe(#37447) (4dfe0fa)SlicePipe(#37447) (4744c22)null(#36259) (#37447) (c7d5555)Code Refactoring
Features
relativeLinkResolutionmigration to update default value (#38698) (15ea811)BREAKING CHANGES
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
slicepipe now returnsnullfor theundefinedinput value,which is consistent with the behavior of most pipes. If you rely on
undefinedbeing the result in that case, you now need to check for itexplicitly.
keyvaluepipe has been fixed to report that forinput objects that have
numberkeys, 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
Maps, so if you need to preservenumbers, this is an effectiveway.
accepted. This should only cause issues in corner cases, as any other
values would result in runtime exceptions.
datepipe now explicitly states which types areaccepted. This should only cause issues in corner cases, as any other
values would result in runtime exceptions.
undefinedfor an input thatwas typed as
undefined. Note that the code actually returnednullonundefinedinputs. In the unlikely case you were relying on this,please fix the typing of the consumers of the pipe output.
map both
nullandundefinedtonulland 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.
NavigationExtrasto 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
NavigationExtraswhich areactually used in the respective function calls or use a type assertion
on the object or variable:
as NavigationExtras.relativeLinkResolutionfrom'legacy'to'default'. If yourapplication previously used the default by not specifying a value in the
ExtraOptionsand uses relative links when navigating from children ofempty path routes, you will need to update your
RouterModuletospecifically specify
'legacy'forrelativeLinkResolution.See https://angular.io/api/router/ExtraOptions#relativeLinkResolution
for more details.
10.1.4 (2020-09-30)
Bug Fixes
Renovate configuration
📅 Schedule: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.
🚦 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 WhiteSource Renovate. View repository job log here.