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
refactor(core): add static-query template strategy #29815
Conversation
73ec857
to
6a72c58
Compare
6a72c58
to
3e43056
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 for the compiler.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approach looks good, some minor changes requested for the printed comment / tests
packages/core/schematics/migrations/static-queries/transform.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/migrations/static-queries/transform.ts
Outdated
Show resolved
Hide resolved
768d41a
to
eecc18b
Compare
65ca60f
to
bf92da0
Compare
In order to support multiple strategies for detecting the query timing, the query usage logic has been moved into a query usage strategy.
The `@angular/compiler` package currently contains the logic for determining whether given queries are used statically or dynamically. This logic would be necessary in order to build a schematic that leverages the Angular compiler API's in order to simulate the query timing based on what ViewEngine computed at compilation-time/runtime. Exporting the logic that is necessary to detect the timing should not affect the public API as the `@angular/compiler` package is denoted as private in `PUBLIC_API.md`
bf92da0
to
4868374
Compare
Introduces a new strategy for the `static-query` schematic that is enabled by default. In order to provide a migration that works for the most Angular applications and makes the upgrade as easy as possible, the template strategy leverages the view engine Angular compiler logic in order to determine the query timing that is currently used within applications using view engine.
4868374
to
3628ce8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
caretaker note: will need a patch to angular BUILD to add dependency |
The `@angular/compiler` package currently contains the logic for determining whether given queries are used statically or dynamically. This logic would be necessary in order to build a schematic that leverages the Angular compiler API's in order to simulate the query timing based on what ViewEngine computed at compilation-time/runtime. Exporting the logic that is necessary to detect the timing should not affect the public API as the `@angular/compiler` package is denoted as private in `PUBLIC_API.md` PR Close #29815
Introduces a new strategy for the `static-query` schematic that is enabled by default. In order to provide a migration that works for the most Angular applications and makes the upgrade as easy as possible, the template strategy leverages the view engine Angular compiler logic in order to determine the query timing that is currently used within applications using view engine. PR Close #29815
In order to support multiple strategies for detecting the query timing, the query usage logic has been moved into a query usage strategy. PR Close angular#29815
The `@angular/compiler` package currently contains the logic for determining whether given queries are used statically or dynamically. This logic would be necessary in order to build a schematic that leverages the Angular compiler API's in order to simulate the query timing based on what ViewEngine computed at compilation-time/runtime. Exporting the logic that is necessary to detect the timing should not affect the public API as the `@angular/compiler` package is denoted as private in `PUBLIC_API.md` PR Close angular#29815
Introduces a new strategy for the `static-query` schematic that is enabled by default. In order to provide a migration that works for the most Angular applications and makes the upgrade as easy as possible, the template strategy leverages the view engine Angular compiler logic in order to determine the query timing that is currently used within applications using view engine. PR Close angular#29815
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Introduces a new strategy for the
static-query
schematic thatis enabled by default. In order to provide a migration that works
for the most Angular applications and makes the upgrade as easy
as possible, the template strategy leverages the view engine
Angular compiler logic in order to determine the same query timing
that is currently used within applications using view engine.