{"push_id":3131837401,"size":19,"distinct_size":2,"ref":"refs/heads/ivy-ngcc-prevent-missing-code","head":"a81caaf14a59ab2d98f45d8f1f8525385042b5bd","before":"9defd7be5e41da3165756169be4d5d25336d1ced","commits":[{"sha":"16d26e5f380d5b4097a14459ae6a11e6caa4fc22","author":{"name":"Isaac Sunkes","email":"aa19b27f273f5e0a9e16ad172151e1c7f61af809@gmail.com"},"message":"docs: add webucator to resources (#26895)\n\nAdded Angular Training by Webucator to Workshops & Onsite Training section of resources.\nPR Close #26895","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/16d26e5f380d5b4097a14459ae6a11e6caa4fc22"},{"sha":"05cdfb90e95a82bed9ee966ce0e7b4b69aa45750","author":{"name":"Andrew Kushnir","email":"5eb74bda639f12d70af58c2a8f8bb773de883ec0@google.com"},"message":"fix(ivy): make ViewRef.detectChanges work with embedded views (FW-749) (#27521)\n\nIn `ViewRef.detectChanges`, we are passing `ViewRef.context` into `detectChanges` to trigger change detection. This only makes sense for component `ViewRefs` (i.e. injected `ChangeDetectorRefs`) because with embedded views, `context` is not a component instance where the view has been monkey-patched. It's a just a normal object, so the view will be undefined.\n\nIn order to resolve this problem, we now invoke `detectChangesInternal` and also pass `LView` (to make sure we always have a view available).\n\nPR Close #27521","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/05cdfb90e95a82bed9ee966ce0e7b4b69aa45750"},{"sha":"bf57e9d78172d39bb5ba0704a51df2fc83c08470","author":{"name":"Alex Eagle","email":"a9a988e0a0d4f5039a0fc8d08f1771dfd55877c6@google.com"},"message":"build: update rules_typescript (#27586)\n\nThis release of rules_typescript fixes a critical bug: typescript code\nwas not checked at all, including type-checking, tsetse, and strict deps\n\nfixes #27569\n\nPR Close #27586","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/bf57e9d78172d39bb5ba0704a51df2fc83c08470"},{"sha":"50687e11cf1173475e9388b290a9bfb0a84c4d17","author":{"name":"Alex Eagle","email":"a9a988e0a0d4f5039a0fc8d08f1771dfd55877c6@google.com"},"message":"build: fix type-check errors introduced during rules_ts 0.21 (#27586)\n\nPR Close #27586","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/50687e11cf1173475e9388b290a9bfb0a84c4d17"},{"sha":"30a3b49830ac937b31b1ae307570ac3821bd7c4b","author":{"name":"Keen Yee Liau","email":"891dd222780bd9d9c4716a6c119d22fcd0600439@umich.edu"},"message":"fix(bazel): Read latest versions from latest-versions.ts & use semver check (#27526)\n\nWhen @angular/bazel is installed, a postinstall script is run to make sure that\nthe npm version is *exactly* the same as the Angular repository install by\nBazel. This check is overly stringent. Instead, it should enforce that the\nversion satisfies the range check instead. This is consistent with the range\ndefined in angular-cli/packages/schematics/angular/utility/latest-versions.ts.\n\nThis commit also fixes the Bazel workspace to use the same Rxjs version if it's\nalready installed.\n\nPR Close #27526","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/30a3b49830ac937b31b1ae307570ac3821bd7c4b"},{"sha":"3290fc3365819bb5069332ae280a2cc5b2a71a67","author":{"name":"Pete Bacon Darwin","email":"e3b6cda228242c30b711ac17cb264f1dbadfd0b6@bacondarwin.com"},"message":"fix(bazel): fix TS errors in the `schematics/bazel-workspace` files (#27600)\n\nUpgrading to the new `ts_library` rule uncovered TS errors in these\nfiles. This commit fixes the code to pass TS checking.\n\nPR Close #27600","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/3290fc3365819bb5069332ae280a2cc5b2a71a67"},{"sha":"fb6a31cbd6222793352ce68a0d7298479ebb290c","author":{"name":"Igor Minar","email":"78b6854e22ab09d4ae3dac29b92052963103b33e@angular.io"},"message":"build: exclude ivy commit messages from the release notes (#27532)\n\nthere is still too much churn to make this info useful in the release notes, advanced\ndevelopers can use git log to find out what's going on with ivy.\n\nPR Close #27532","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/fb6a31cbd6222793352ce68a0d7298479ebb290c"},{"sha":"3cb6dad6d58ac9c5b82847576e8f79f205002704","author":{"name":"Michał Jawulski","email":"b33cd6b15a06fd5505963ab919eb4e8d13c273c4@gmail.com"},"message":"docs: update npm scripts to support angular 7 (#27334)\n\nPR Close #27334","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/3cb6dad6d58ac9c5b82847576e8f79f205002704"},{"sha":"ceb14deb60691c73eeb99f6272624f23aadc6481","author":{"name":"Andrew Kushnir","email":"5eb74bda639f12d70af58c2a8f8bb773de883ec0@google.com"},"message":"fix(ivy): proper slot allocation for pure functions in `hostBindings` function (#27587)\n\nPrior to this update, we always returned the number of host vars defined in @Component definition as a value for `allocatePureFunctionsSlot` callback in ValueConverter. As a result, pure function arguments were not accounted for, thus leasing to incorrect slot offsets in `pureFunction` calls. Now we update and return total # of host vars, so the offsets are defined correctly.\n\nPR Close #27587","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/ceb14deb60691c73eeb99f6272624f23aadc6481"},{"sha":"452668b581d3bf9e0b72f4a16da12ec9dabe4b67","author":{"name":"Kara Erickson","email":"d133a09d71c4b4234768590f5d12819c3b0830dc@google.com"},"message":"fix(ivy): host bindings should work if input has same name (#27589)\n\nPreviously in Ivy, host bindings did not work if they shared a public name\nwith an Input because they used the `elementProperty` instruction as is.\nThis instruction was originally built for inside component templates, so it\nwould either set a directive input OR a native property. This is the\ncorrect behavior for inside a template, but for host bindings, we always\nwant the native properties to be set regardless of the presence of an Input.\n\nThis change adds an extra argument to `elementProperty` so we can tell it to\nignore directive inputs and only set native properties (if it is in the\ncontext of a host binding).\n\nPR Close #27589","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/452668b581d3bf9e0b72f4a16da12ec9dabe4b67"},{"sha":"69806316316c634a12a1c4cc1199baff39d41f8a","author":{"name":"Pawel Kozlowski","email":"e93abf4e471b18d410f233bcd309156a9365cee9@gmail.com"},"message":"test(ivy): update root causes for @angular/core TestBed failures (#27602)\n\nPR Close #27602","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/69806316316c634a12a1c4cc1199baff39d41f8a"},{"sha":"053b43d3085d6caff19dc2361dd9994d64a23392","author":{"name":"Kara Erickson","email":"d133a09d71c4b4234768590f5d12819c3b0830dc@google.com"},"message":"fix(ivy): update new host binding test with instruction change (#27605)\n\nThe pure functions in host bindings change was merged after the change in\nhost binding instructions, so it had a new test that wasn't yet updated\nwith the new generated code. This commit updates the new test.\n\nPR Close #27605","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/053b43d3085d6caff19dc2361dd9994d64a23392"},{"sha":"098a7871610e24a6afbe2e24500bdfb29fd84034","author":{"name":"Alex Rickabaugh","email":"6e7b2a2739bf23d08125acba0ec619d24b531bae@alxandria.net"},"message":"docs: release notes for the v7.1.3 release","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/098a7871610e24a6afbe2e24500bdfb29fd84034"},{"sha":"b69ec48d7759fda9a06c8da96c15f7293d711160","author":{"name":"Alex Rickabaugh","email":"6e7b2a2739bf23d08125acba0ec619d24b531bae@alxandria.net"},"message":"release: cut the v7.2.0-beta.2 release","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/b69ec48d7759fda9a06c8da96c15f7293d711160"},{"sha":"dc1ed3c47e2d9fab196a745df5152e149c65211f","author":{"name":"Lucas","email":"44b369e2db3849f66325fb815cdfa8927e1343b2@users.noreply.github.com"},"message":"docs: fix ngModel typo in form validation guide (#27574)\n\nFix typo\n\nPR Close #27574","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/dc1ed3c47e2d9fab196a745df5152e149c65211f"},{"sha":"93820b493c41d8907fb660d837419ac5a4fd16e5","author":{"name":"Igor Minar","email":"78b6854e22ab09d4ae3dac29b92052963103b33e@angular.io"},"message":"build: bump @bazel/ibazel to 0.9.0 (#27601)\n\nThis should fix the problem with ibazel crashing on bzl/BUILD file syntax errors. bazelbuild/bazel-watcher/issues/194\n\nhttps://github.com/bazelbuild/bazel-watcher/blob/master/CHANGELOG.md#v090-2018-12-07\n\nPR Close #27601","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/93820b493c41d8907fb660d837419ac5a4fd16e5"},{"sha":"cabf1c71059140a2f7855790a9e8ea79b6745f3a","author":{"name":"Igor Minar","email":"78b6854e22ab09d4ae3dac29b92052963103b33e@angular.io"},"message":"docs: update SAVED_REPLIES and CONTRIBUTING with new issue templates (#27608)\n\nWhen we launched the new issue templates (.github/ISSUE_TEMPLATE/*), we forgot to update these\ndocs which got stale and needed a refresh.\n\nPR Close #27608","distinct":false,"url":"https://api.github.com/repos/JoostK/angular/commits/cabf1c71059140a2f7855790a9e8ea79b6745f3a"},{"sha":"3090068e945bcce0725486ad35f44ec6b60176d6","author":{"name":"JoostK","email":"9582526047874b3a242a49412ddc0f68c4590ec5@gmail.com"},"message":"fix(ivy): prevent ngcc from inadvertently dropping Ivy definitions\n\nA surprising interaction with the MagicString library caused inserted\nIvy definitions to be dropped during the removal of decorators, iff all\ndecorators on the class could be removed. In that case, the removal\nlocation corresponds with the exact location where Ivy definitions were\ninserted into.\n\nThis commit moves the removal of decorators to occur before Ivy\ndefinitions are inserted. This effectively avoids the problem, as later\ninserted text fragments will be retained by MagicString.","distinct":true,"url":"https://api.github.com/repos/JoostK/angular/commits/3090068e945bcce0725486ad35f44ec6b60176d6"},{"sha":"a81caaf14a59ab2d98f45d8f1f8525385042b5bd","author":{"name":"JoostK","email":"9582526047874b3a242a49412ddc0f68c4590ec5@gmail.com"},"message":"fixup! fix(ivy): prevent ngcc from inadvertently dropping Ivy definitions","distinct":true,"url":"https://api.github.com/repos/JoostK/angular/commits/a81caaf14a59ab2d98f45d8f1f8525385042b5bd"}]}
{"actor":{"display_login":"alxhub"}}