{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":24195339,"defaultBranch":"main","name":"angular","ownerLogin":"angular","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2014-09-18T16:12:01.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/139426?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1715906535.0","currentOid":""},"activityList":{"items":[{"before":"cae0d3167daa5a166380256d34a0d1aab5d1ac50","after":"f7894885b80dbdca99877569ea98aac2dc175e6c","ref":"refs/heads/g3","pushedAt":"2024-05-17T20:37:19.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"copybara-service[bot]","name":null,"path":"/apps/copybara-service","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/44061?s=80&v=4"},"commit":{"message":"refactor(core): Cleanup dead jsnamespace code (#55795)\n\nSupport for the jsnamespace attribute was removed in #55619.\n\nPR Close #55795","shortMessageHtmlLink":"refactor(core): Cleanup dead jsnamespace code (#55795)"}},{"before":"a78144ac2169e1108d5ccf5b1fe52ba8aa6586aa","after":"239d4f0c9ea7da1ce220e5b4842b00b0bcecdfc6","ref":"refs/heads/18.0.x","pushedAt":"2024-05-17T19:59:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"refactor(core): Cleanup dead jsnamespace code (#55795)\n\nSupport for the jsnamespace attribute was removed in #55619.\n\nPR Close #55795","shortMessageHtmlLink":"refactor(core): Cleanup dead jsnamespace code (#55795)"}},{"before":"b89c88c73bfd98fcda704a836f1943a6f7116a79","after":"f7894885b80dbdca99877569ea98aac2dc175e6c","ref":"refs/heads/main","pushedAt":"2024-05-17T19:59:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"refactor(core): Cleanup dead jsnamespace code (#55795)\n\nSupport for the jsnamespace attribute was removed in #55619.\n\nPR Close #55795","shortMessageHtmlLink":"refactor(core): Cleanup dead jsnamespace code (#55795)"}},{"before":"9884875c9698028c5788ad150239e4c52109b87d","after":"cae0d3167daa5a166380256d34a0d1aab5d1ac50","ref":"refs/heads/g3","pushedAt":"2024-05-17T19:53:48.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"copybara-service[bot]","name":null,"path":"/apps/copybara-service","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/44061?s=80&v=4"},"commit":{"message":"fix(core): exhaustive checkNoChanges should only do a single pass (#55839)\n\nBecause exhaustive checks traverse the whole tree regardless of the\ndirty state, it breaks some expectations around how change detection\nshould be running. When a view has transplanted views, it\nunconditionally marks all ancestors for traversal, assuming this is fine\nbecause the loop will just traverse them and find nothing dirty.\nHowever, exhaustive checkNoChanages actually refreshes everything during\ntraversal.\n\nThis update ensures the exhaustive check only does a single pass and\nalso prevents some unnecessary marking of transplanted views for\nrefresh since we know they're going to be reached.\n\nPR Close #55839","shortMessageHtmlLink":"fix(core): exhaustive checkNoChanges should only do a single pass (#5…"}},{"before":"f0f85dbe2f4c437ebe080ead60ebd6bfb7ea491e","after":"a78144ac2169e1108d5ccf5b1fe52ba8aa6586aa","ref":"refs/heads/18.0.x","pushedAt":"2024-05-17T19:25:47.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"docs: fix broken link in signals/model (#55811)\nPR Close #55811","shortMessageHtmlLink":"docs: fix broken link in signals/model (#55811)"}},{"before":"7aadf424661b987054a7cb1168f0ee4bddd5195a","after":"b89c88c73bfd98fcda704a836f1943a6f7116a79","ref":"refs/heads/main","pushedAt":"2024-05-17T19:25:47.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"docs: fix broken link in signals/model (#55811)\nPR Close #55811","shortMessageHtmlLink":"docs: fix broken link in signals/model (#55811)"}},{"before":"cae0d3167daa5a166380256d34a0d1aab5d1ac50","after":"7aadf424661b987054a7cb1168f0ee4bddd5195a","ref":"refs/heads/main","pushedAt":"2024-05-17T19:25:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"docs: Include info about experimental on adev (#55857)\n\nCopy information about meaning of \"experimental\"\nfrom angular.io to angular.dev.\n\nPR Close #55857","shortMessageHtmlLink":"docs: Include info about experimental on adev (#55857)"}},{"before":"0147e0b85a4f1201b1ae5edaa0d2bc708a13673e","after":"f0f85dbe2f4c437ebe080ead60ebd6bfb7ea491e","ref":"refs/heads/18.0.x","pushedAt":"2024-05-17T19:25:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"docs: Include info about experimental on adev (#55857)\n\nCopy information about meaning of \"experimental\"\nfrom angular.io to angular.dev.\n\nPR Close #55857","shortMessageHtmlLink":"docs: Include info about experimental on adev (#55857)"}},{"before":"8d93597a82860112a5398828745653a7e27dcef0","after":"0147e0b85a4f1201b1ae5edaa0d2bc708a13673e","ref":"refs/heads/18.0.x","pushedAt":"2024-05-17T19:24:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"fix(core): exhaustive checkNoChanges should only do a single pass (#55839)\n\nBecause exhaustive checks traverse the whole tree regardless of the\ndirty state, it breaks some expectations around how change detection\nshould be running. When a view has transplanted views, it\nunconditionally marks all ancestors for traversal, assuming this is fine\nbecause the loop will just traverse them and find nothing dirty.\nHowever, exhaustive checkNoChanages actually refreshes everything during\ntraversal.\n\nThis update ensures the exhaustive check only does a single pass and\nalso prevents some unnecessary marking of transplanted views for\nrefresh since we know they're going to be reached.\n\nPR Close #55839","shortMessageHtmlLink":"fix(core): exhaustive checkNoChanges should only do a single pass (#5…"}},{"before":"9884875c9698028c5788ad150239e4c52109b87d","after":"cae0d3167daa5a166380256d34a0d1aab5d1ac50","ref":"refs/heads/main","pushedAt":"2024-05-17T19:24:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"fix(core): exhaustive checkNoChanges should only do a single pass (#55839)\n\nBecause exhaustive checks traverse the whole tree regardless of the\ndirty state, it breaks some expectations around how change detection\nshould be running. When a view has transplanted views, it\nunconditionally marks all ancestors for traversal, assuming this is fine\nbecause the loop will just traverse them and find nothing dirty.\nHowever, exhaustive checkNoChanages actually refreshes everything during\ntraversal.\n\nThis update ensures the exhaustive check only does a single pass and\nalso prevents some unnecessary marking of transplanted views for\nrefresh since we know they're going to be reached.\n\nPR Close #55839","shortMessageHtmlLink":"fix(core): exhaustive checkNoChanges should only do a single pass (#5…"}},{"before":"400911e3b8d3c36ff788495bd7ecfd75b197c549","after":"9884875c9698028c5788ad150239e4c52109b87d","ref":"refs/heads/g3","pushedAt":"2024-05-17T18:15:23.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"copybara-service[bot]","name":null,"path":"/apps/copybara-service","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/44061?s=80&v=4"},"commit":{"message":"fix(compiler-cli): fix type narrowing of `@if` with aliases (#55835)\n\nWhen an `@if` expression has an alias, only the type of the alias is\ncurrently narrowed. So for example, suppose `value` is `string|undefined`:\n\n```\n@if (value; as alias) {\n {{ value.length }} \n {{ alias.length }} \n}\n```\n\nThis is especially noticeable when the expression contains guards which are\npreconditions for the aliased expression:\n\n```\n@if (a && b; as alias) {...}\n```\n\nIn this case, `a` would not be narrowed within the body, even though the\n`@if` condition forces it to be truthy. This is a bug.\n\nThe reason is that aliased expressions were previously type-checked as:\n\n```\nvar alias = a && b;\nif (alias) {\n // nothing other than alias is narrowed\n ...\n}\n```\n\nOne option considered was to emit `const alias` instead of `var alias`.\nTypeScript _does_ trace `const` expressions and narrow their individual\ncomponents when the overall expression is guarded:\n\n```\nconst alias = a && b;\nif (alias) {\n // a, b are also narrowed\n}\n```\n\nHowever, this narrowing has different semantics than if `a && b` appeared\ndirectly in the guard expression. For example, object properties aren't\nnarrowed with this approach, so component properties (which are referenced\nas e.g. `this.a`) would not be narrowed.\n\nInstead, we amend the guard expression to include both the expression _and_ the\nalias variable, enforcing that both are narrowed.\n\n```\nvar alias = a && b;\nif ((a && b) && alias) {\n // a, b, and alias all narrowed correctly.\n}\n```\n\nThis form ensures all conditions within the guard expression get narrowed\nwhile also narrowing the alias variable type.\n\nFixes #52855\n\nPR Close #55835","shortMessageHtmlLink":"fix(compiler-cli): fix type narrowing of @if with aliases (#55835)"}},{"before":"0e16654be48bb325a45ceb3e5cd292781d6d316d","after":"8d93597a82860112a5398828745653a7e27dcef0","ref":"refs/heads/18.0.x","pushedAt":"2024-05-17T17:15:11.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"fix(compiler-cli): fix type narrowing of `@if` with aliases (#55835)\n\nWhen an `@if` expression has an alias, only the type of the alias is\ncurrently narrowed. So for example, suppose `value` is `string|undefined`:\n\n```\n@if (value; as alias) {\n {{ value.length }} \n {{ alias.length }} \n}\n```\n\nThis is especially noticeable when the expression contains guards which are\npreconditions for the aliased expression:\n\n```\n@if (a && b; as alias) {...}\n```\n\nIn this case, `a` would not be narrowed within the body, even though the\n`@if` condition forces it to be truthy. This is a bug.\n\nThe reason is that aliased expressions were previously type-checked as:\n\n```\nvar alias = a && b;\nif (alias) {\n // nothing other than alias is narrowed\n ...\n}\n```\n\nOne option considered was to emit `const alias` instead of `var alias`.\nTypeScript _does_ trace `const` expressions and narrow their individual\ncomponents when the overall expression is guarded:\n\n```\nconst alias = a && b;\nif (alias) {\n // a, b are also narrowed\n}\n```\n\nHowever, this narrowing has different semantics than if `a && b` appeared\ndirectly in the guard expression. For example, object properties aren't\nnarrowed with this approach, so component properties (which are referenced\nas e.g. `this.a`) would not be narrowed.\n\nInstead, we amend the guard expression to include both the expression _and_ the\nalias variable, enforcing that both are narrowed.\n\n```\nvar alias = a && b;\nif ((a && b) && alias) {\n // a, b, and alias all narrowed correctly.\n}\n```\n\nThis form ensures all conditions within the guard expression get narrowed\nwhile also narrowing the alias variable type.\n\nFixes #52855\n\nPR Close #55835","shortMessageHtmlLink":"fix(compiler-cli): fix type narrowing of @if with aliases (#55835)"}},{"before":"eddb4051b831a91141cc41ab260180036bfaf342","after":"9884875c9698028c5788ad150239e4c52109b87d","ref":"refs/heads/main","pushedAt":"2024-05-17T17:15:11.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"fix(compiler-cli): fix type narrowing of `@if` with aliases (#55835)\n\nWhen an `@if` expression has an alias, only the type of the alias is\ncurrently narrowed. So for example, suppose `value` is `string|undefined`:\n\n```\n@if (value; as alias) {\n {{ value.length }} \n {{ alias.length }} \n}\n```\n\nThis is especially noticeable when the expression contains guards which are\npreconditions for the aliased expression:\n\n```\n@if (a && b; as alias) {...}\n```\n\nIn this case, `a` would not be narrowed within the body, even though the\n`@if` condition forces it to be truthy. This is a bug.\n\nThe reason is that aliased expressions were previously type-checked as:\n\n```\nvar alias = a && b;\nif (alias) {\n // nothing other than alias is narrowed\n ...\n}\n```\n\nOne option considered was to emit `const alias` instead of `var alias`.\nTypeScript _does_ trace `const` expressions and narrow their individual\ncomponents when the overall expression is guarded:\n\n```\nconst alias = a && b;\nif (alias) {\n // a, b are also narrowed\n}\n```\n\nHowever, this narrowing has different semantics than if `a && b` appeared\ndirectly in the guard expression. For example, object properties aren't\nnarrowed with this approach, so component properties (which are referenced\nas e.g. `this.a`) would not be narrowed.\n\nInstead, we amend the guard expression to include both the expression _and_ the\nalias variable, enforcing that both are narrowed.\n\n```\nvar alias = a && b;\nif ((a && b) && alias) {\n // a, b, and alias all narrowed correctly.\n}\n```\n\nThis form ensures all conditions within the guard expression get narrowed\nwhile also narrowing the alias variable type.\n\nFixes #52855\n\nPR Close #55835","shortMessageHtmlLink":"fix(compiler-cli): fix type narrowing of @if with aliases (#55835)"}},{"before":"f8a6ebd9772baad137ad8c677faf53c37b7c4a0a","after":"0e16654be48bb325a45ceb3e5cd292781d6d316d","ref":"refs/heads/18.0.x","pushedAt":"2024-05-17T17:12:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"refactor(forms): remove deprecated symbols (#55723)\n\nFollow-up of #55698 to help remove the symbols from G3.\n\nPR Close #55723","shortMessageHtmlLink":"refactor(forms): remove deprecated symbols (#55723)"}},{"before":"0e23ed716ed99ff0ab607d370694fff85d1ee1e8","after":"eddb4051b831a91141cc41ab260180036bfaf342","ref":"refs/heads/main","pushedAt":"2024-05-17T17:12:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"refactor(forms): remove deprecated symbols (#55723)\n\nFollow-up of #55698 to help remove the symbols from G3.\n\nPR Close #55723","shortMessageHtmlLink":"refactor(forms): remove deprecated symbols (#55723)"}},{"before":"13601105ec06f114d3ee13d4bfd42ebf0793f135","after":"0e23ed716ed99ff0ab607d370694fff85d1ee1e8","ref":"refs/heads/main","pushedAt":"2024-05-17T17:10:12.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"docs: Add documentation for event replay (#55802)\n\nPR Close #55802","shortMessageHtmlLink":"docs: Add documentation for event replay (#55802)"}},{"before":"69a83993b3772dd98cc10d3e12b0ca6c66293cf2","after":"f8a6ebd9772baad137ad8c677faf53c37b7c4a0a","ref":"refs/heads/18.0.x","pushedAt":"2024-05-17T17:10:12.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"docs: Add documentation for event replay (#55802)\n\nPR Close #55802","shortMessageHtmlLink":"docs: Add documentation for event replay (#55802)"}},{"before":null,"after":"57bc4bbdd54ecda0ca648221f74532f80cb7effd","ref":"refs/heads/dylhunn-patch-1","pushedAt":"2024-05-17T00:34:06.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"docs(zone.js): update release guide for zone.js\n\nUpdate the releasing guide for zone.js, because one of the release commands was outdated.","shortMessageHtmlLink":"docs(zone.js): update release guide for zone.js"}},{"before":"400911e3b8d3c36ff788495bd7ecfd75b197c549","after":"13601105ec06f114d3ee13d4bfd42ebf0793f135","ref":"refs/heads/main","pushedAt":"2024-05-17T00:32:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"release: cut the zone.js-0.14.6 release (#55845)\n\nPR Close #55845","shortMessageHtmlLink":"release: cut the zone.js-0.14.6 release (#55845)"}},{"before":null,"after":"4c01a080a337afa648abd506328f010581a12b26","ref":"refs/heads/dylhunn-zonejs-instructions","pushedAt":"2024-05-16T23:31:53.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"dylhunn","name":"Dylan Hunn","path":"/dylhunn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7135246?s=80&v=4"},"commit":{"message":"dev-infra: update DEVELOPER.md release instructions for zone.js\n\nThe previous instructions were stale. I have updated them to better reflect current processes.","shortMessageHtmlLink":"dev-infra: update DEVELOPER.md release instructions for zone.js"}},{"before":"53b0d6adb838705755ba7e260e7ff5c824c84d85","after":"400911e3b8d3c36ff788495bd7ecfd75b197c549","ref":"refs/heads/g3","pushedAt":"2024-05-16T17:57:57.000Z","pushType":"push","commitsCount":10,"pusher":{"login":"copybara-service[bot]","name":null,"path":"/apps/copybara-service","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/44061?s=80&v=4"},"commit":{"message":"fix(compiler-cli): do not throw when retrieving TCB symbol for signal input with restricted access (#55774)\n\nCurrently when attempting to retrieve a TCB symbol for an input binding\nthat refers to a signal input with e.g. `protected`, while the\n`honorAccessModifiersForInputBindings` flag is `false`, Angular will\nthrow a runtime exception because the symbol retrieval code always\nexpects a proper field access in the TCB.\n\nThis is not the case with `honorAccessModifiersForInputBindings =\nfalse`, as TCB will allocate a temporary variable when ignoring the\nfield access. This will then trigger the runtime exception (which we\nadded to flag such \"unexpected\" cases). This commit handles it\ngracefully, as it's valid TCB, but we simply cannot generate a proper\nTCB symbol (yet). This is similar to `@Input` decorator inputs.\n\nIn the future we may implement logic to build up TCB symbols for\nnon-property access bindings, for both signal inputs or `@Input`\ninputs. This commit just avoids a build exception.\n\nRelated to: #54324.\n\nPR Close #55774","shortMessageHtmlLink":"fix(compiler-cli): do not throw when retrieving TCB symbol for signal…"}},{"before":"abdf453b85477ace0d6a3ddebeb3663edc1629bc","after":"400911e3b8d3c36ff788495bd7ecfd75b197c549","ref":"refs/heads/main","pushedAt":"2024-05-16T16:33:04.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"fix(compiler-cli): do not throw when retrieving TCB symbol for signal input with restricted access (#55774)\n\nCurrently when attempting to retrieve a TCB symbol for an input binding\nthat refers to a signal input with e.g. `protected`, while the\n`honorAccessModifiersForInputBindings` flag is `false`, Angular will\nthrow a runtime exception because the symbol retrieval code always\nexpects a proper field access in the TCB.\n\nThis is not the case with `honorAccessModifiersForInputBindings =\nfalse`, as TCB will allocate a temporary variable when ignoring the\nfield access. This will then trigger the runtime exception (which we\nadded to flag such \"unexpected\" cases). This commit handles it\ngracefully, as it's valid TCB, but we simply cannot generate a proper\nTCB symbol (yet). This is similar to `@Input` decorator inputs.\n\nIn the future we may implement logic to build up TCB symbols for\nnon-property access bindings, for both signal inputs or `@Input`\ninputs. This commit just avoids a build exception.\n\nRelated to: #54324.\n\nPR Close #55774","shortMessageHtmlLink":"fix(compiler-cli): do not throw when retrieving TCB symbol for signal…"}},{"before":"6025424fea43ca56b0c9f520e5e97887ae59037c","after":"69a83993b3772dd98cc10d3e12b0ca6c66293cf2","ref":"refs/heads/18.0.x","pushedAt":"2024-05-16T16:33:04.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"fix(compiler-cli): do not throw when retrieving TCB symbol for signal input with restricted access (#55774)\n\nCurrently when attempting to retrieve a TCB symbol for an input binding\nthat refers to a signal input with e.g. `protected`, while the\n`honorAccessModifiersForInputBindings` flag is `false`, Angular will\nthrow a runtime exception because the symbol retrieval code always\nexpects a proper field access in the TCB.\n\nThis is not the case with `honorAccessModifiersForInputBindings =\nfalse`, as TCB will allocate a temporary variable when ignoring the\nfield access. This will then trigger the runtime exception (which we\nadded to flag such \"unexpected\" cases). This commit handles it\ngracefully, as it's valid TCB, but we simply cannot generate a proper\nTCB symbol (yet). This is similar to `@Input` decorator inputs.\n\nIn the future we may implement logic to build up TCB symbols for\nnon-property access bindings, for both signal inputs or `@Input`\ninputs. This commit just avoids a build exception.\n\nRelated to: #54324.\n\nPR Close #55774","shortMessageHtmlLink":"fix(compiler-cli): do not throw when retrieving TCB symbol for signal…"}},{"before":"eba92cfa55500f3558c02edd0aa348ae118794e0","after":"6025424fea43ca56b0c9f520e5e97887ae59037c","ref":"refs/heads/18.0.x","pushedAt":"2024-05-16T16:32:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"docs: Update build system migration title to reflect user action (#55782)\n\nThe Angular CLI documentation topic for migrating to the new build system\nnow has a navigation label of \"Migrating to new build system\" instead of\n\"esbuild\". This new label better reflects the action a user may want to\ntake rather than one of the tools used by the new build system.\n\nPR Close #55782","shortMessageHtmlLink":"docs: Update build system migration title to reflect user action (#55782"}},{"before":"2bb12ac02f8a0f766f6a38d4f3704eaebe58d402","after":"abdf453b85477ace0d6a3ddebeb3663edc1629bc","ref":"refs/heads/main","pushedAt":"2024-05-16T16:32:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"docs: Update build system migration title to reflect user action (#55782)\n\nThe Angular CLI documentation topic for migrating to the new build system\nnow has a navigation label of \"Migrating to new build system\" instead of\n\"esbuild\". This new label better reflects the action a user may want to\ntake rather than one of the tools used by the new build system.\n\nPR Close #55782","shortMessageHtmlLink":"docs: Update build system migration title to reflect user action (#55782"}},{"before":"20a530acb6ca6efe73cb97c64e9d23a0f5d912c8","after":"2bb12ac02f8a0f766f6a38d4f3704eaebe58d402","ref":"refs/heads/main","pushedAt":"2024-05-16T16:28:14.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"fix(compiler): prevent usage of reserved control flow symbol in custom interpolation context. (#55809)\n\n* Fixes the issue where using a reserved control flow @ symbol in a custom interpolation context yields improper parser feedback.\n\nPR Close #55809","shortMessageHtmlLink":"fix(compiler): prevent usage of reserved control flow symbol in custo…"}},{"before":"3055b924afcb2d94ace11072beffa196882b77df","after":"eba92cfa55500f3558c02edd0aa348ae118794e0","ref":"refs/heads/18.0.x","pushedAt":"2024-05-16T16:28:14.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"fix(compiler): prevent usage of reserved control flow symbol in custom interpolation context. (#55809)\n\n* Fixes the issue where using a reserved control flow @ symbol in a custom interpolation context yields improper parser feedback.\n\nPR Close #55809","shortMessageHtmlLink":"fix(compiler): prevent usage of reserved control flow symbol in custo…"}},{"before":"f3b0e2fbc124559cecbeb81cce25785c60e066bf","after":"20a530acb6ca6efe73cb97c64e9d23a0f5d912c8","ref":"refs/heads/main","pushedAt":"2024-05-16T16:21:19.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"fix(zone.js): correctly bundle `zone-patch-rxjs` (#55826)\n\nhttps://github.com/angular/angular/pull/53443 caused the a local `rxjs` file to be imported from an entry-point which caused this to be excluded from being bundled due to the name matching `rxjs`.\n\nCloses #55825\n\nPR Close #55826","shortMessageHtmlLink":"fix(zone.js): correctly bundle zone-patch-rxjs (#55826)"}},{"before":"a768c90ee744027a50114736949def7527d9392b","after":"3055b924afcb2d94ace11072beffa196882b77df","ref":"refs/heads/18.0.x","pushedAt":"2024-05-16T16:21:19.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"fix(zone.js): correctly bundle `zone-patch-rxjs` (#55826)\n\nhttps://github.com/angular/angular/pull/53443 caused the a local `rxjs` file to be imported from an entry-point which caused this to be excluded from being bundled due to the name matching `rxjs`.\n\nCloses #55825\n\nPR Close #55826","shortMessageHtmlLink":"fix(zone.js): correctly bundle zone-patch-rxjs (#55826)"}},{"before":"45badde88c145d554687884d909436aa5bd1147d","after":"349f24af5617f1633a6f9d9556febae26859f52e","ref":"refs/heads/17.3.x","pushedAt":"2024-05-16T16:15:42.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"atscott","name":"Andrew Scott","path":"/atscott","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/479713?s=80&v=4"},"commit":{"message":"refactor(zone.js): remove `tslib` from `dependencies` (#55827)\n\nIif needed `tslib` code is included directly in the bundled FESM2015 hence making the dependency redundant.\n\nPR Close #55827","shortMessageHtmlLink":"refactor(zone.js): remove tslib from dependencies (#55827)"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAETUchlwA","startCursor":null,"endCursor":null}},"title":"Activity · angular/angular"}