Convert Material and CDK to standalone#28155
Conversation
6eb58a8 to
bf32b8f
Compare
43b379a to
6c4f888
Compare
…ormat Converts test components in the CDK to standalone and fixes some that weren't formatteed according to the Prettier config.
Converts `cdk/a11y` to standalone.
Converts `cdk/accordion` to standalone.
Converts `cdk/bidi` to standalone.
Converts `cdk/clipboard` to standalone.
Converts `cdk/portal` to standalone.
Converts `cdk/stepper` to standalone.
Converts `cdk/table` to standalone.
Converts `cdk/text-field` to standalone.
Converts `cdk/tree` to standalone.
Converts `cdk/observers` to standalone.
Converts `material/autocomplete` to standalone.
Converts `material/badge` to standalone.
Converts `material/bottom-sheet` to standalone.
Converts `material/button` to standalone.
Converts `material/button-toggle` to standalone.
|
Blocked on angular/angular#53097. |
During the presubmit of angular/components#28155 an internal check started flagging the `setAttribute` call inside `relativePath`. This code has been here for many years, but I suspect that the import graph changing caused it to be surfaced. Ideally we would refactor this code not to create a DOM node at all, but for now this is the simplest approach to unblock the change in Material.
… path Currently the way we extract the pathname of a URL is by creating an anchor node, assigning the URL to its `href` and reading the `pathname`. This is inefficient and it triggers an internal security check that doesn't allow the `href` attribute to be set which ends up blocking angular/components#28155. These changes switch to using the browser's built-in URL parsing instead.
|
I have a question: Are all material components suitable for conversion to standalone components? I want to know what you think :) |
|
There's nothing stopping you from continuing to use the |
… path (#53097) Currently the way we extract the pathname of a URL is by creating an anchor node, assigning the URL to its `href` and reading the `pathname`. This is inefficient and it triggers an internal security check that doesn't allow the `href` attribute to be set which ends up blocking angular/components#28155. These changes switch to using the browser's built-in URL parsing instead. PR Close #53097
… path (#53097) Currently the way we extract the pathname of a URL is by creating an anchor node, assigning the URL to its `href` and reading the `pathname`. This is inefficient and it triggers an internal security check that doesn't allow the `href` attribute to be set which ends up blocking angular/components#28155. These changes switch to using the browser's built-in URL parsing instead. PR Close #53097
Cherry-picks some of the changes from angular#28155 to the patch branch since they're necessary for compatibility with `@defer`. Fixes angular#28198.
|
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. |
Converts all of Material and the remaining non-standalone directives in the CDK to standalone. Note that there's more work to be done like fixing up tests and updating public APIs to be more standalone-friendly.