angular / components

…migration (#22741)

Adding support for extra variables to handle some Google-internal variables that need to be migrated as well.

…over styles; fix sticky columns (#22723)

* fix(material-experimental/mdc-table): add background color; disable hover styles; fix sticky columns

* fix(material-experimental/mdc-table): lint

* fix(material-experimental/mdc-table): extra line

…ose all themes (#22449)

When I was setting up the new theming API for MDC, I assumed that the button theme would include the icon button and fab themes as well, but that's not the case.
These changes reorganize the button theming styles into separate files so that we can easily expose the missing mixins under the correct prefix.

We recently updated to `rules_nodejs` 3.5.0. This contained a fix
for something we recently tried to achieve using a postinstall
patch. The PR that updated to 3.5.0 became a little out-of-date
due to the PR introducing the postinstall patch being merged, so
that the failure only surfaced when the update PR got merged.

…-http-example (#22053)" (#22725)

This reverts commit 67dc1fd.

…ayer` package (#22710)

Currently if developers run `ng update` without specifying a package,
the CLI will analyze the current workspace and find packages that
provide migrations and need to be updated. For the `youtube-player`
and `google-maps` package we do not provide any migrations, so
`ng update` will not report this package.

Since these packages are part of the `@angular` scope, we
want these packages to be highlighted when users run `ng update`.
There aren't any migrations for these packages yet, but we are setting
up the integration with `ng update` in order to make these packages
visible to the CLI.

Fixes #22689.

Updates to the latest version of `rules_nodejs` that contains
various fixes for Windows. The linker has been preventing windows
developers from running tests reliably. This has been fixed with:

bazelbuild/rules_nodejs@7cf7d73

* docs(material/tree): A11Y improvement for Nested Tree example.

Fixes #22517

* docs(material/tree): A11Y improvement for Nested Tree example.

Fixes #22517

* docs(material/tree): Fixing nested tree styles.
Use padding-left instead of padding-inline-start.

* build: update the comment of workspace for bazel version

The minimum bazel version to use with this repo is v4.0.0.

* build: remove the comment `# The minimum bazel version to use with this repo is v3.1.0.`

remove the `# The minimum bazel version to use with this repo is v3.1.0.`, the code is pretty self-explanatory

related #21722

…op animations are enabled (#22651)

Fixes that the MDC-based radio button didn't disable its animations when noop animations were turned on.

…abled under noop animations module (#22661)

Fixes that the buffer bar in the MDC-based `mat-progress-bar` still animates when animations are disabled.

#22684)

* fix(material-experimental/mdc-slider): make small fixes needed to implement the gmat mdc slider internally

* change imports of @material/base to @material/base/types
* explicitly check attributes when calling setAttribute to prevent xss

* fixup! fix(material-experimental/mdc-slider): make small fixes needed to implement the gmat mdc slider internally

* fixup! fix(material-experimental/mdc-slider): make small fixes needed to implement the gmat mdc slider internally

* fixup! fix(material-experimental/mdc-slider): make small fixes needed to implement the gmat mdc slider internally

…abel position (#22696)

The strong focus indicator renders using a `::before` selector which is also used for styling a stepper header with a `below` label position. This results in broken styles when strong focus indication is enabled.

These changes move the indicator to a different element.

Fixes #22677.

…migration

Currently the theming API migration drops any imports starting with `~@angular/material/`, assuming that they're Sass APIs. This can result in prebuilt style imports being removed by mistake.

These changes add a regex based on which we'll exclude some imports from the migration.

Fixes #22697.

…22641)

Fixes that the tooltip won't update its position config if the directionality changes after it has been initialized.

We have a call to `Injector.get` in the date range input which is supposed to fall back to `null` if the value doesn't resolve, however we're missing the `Optional` flag. It works by accident at the moment, because the inject flags aren't actually being passed through by the framework.

angular/angular#41592 is supposed to fix the framework issue, but their CI will break due to our usage.

These changes fix our usage in order to unblock the framework PR.

…quired for the legacy theming bundle

…for the legacy theming bundle

Currently the legacy `material/theming` bundle is set up to forward a few top-level `.import` files. The problem is that those files have been auto-generated to be backwards-compatible even for deep imports which means that they have a lot of overlapping `@forward` and `@import` statements. This results in a significant increase in build times for consumers still using the old bundle.

These changes address the issue by introducing new shallower `*-legacy-index.scss` files which only export the APIs from the specific package and which in turn are re-exported through the top-level `material/theming` file. The change appears to cut the down the production build time on material.angular.io before the @use migration by more than 60%.

Fixes #22676.

…ge directionality (#22705)

On the first iteration of the MDC progress bar we had to use JS to change the direction in RTL, but a few months ago in #21650 we switched to a different API that no longer depends on it. The problem with the changes in #21650 is that they set the `dir` on the progress bar in order to flip its direction for the `query` mode.

These changes simplify the setup by relying only on CSS to determine the direction.

Fixes #22609.

* build: add tests to ensure compatibility with ng-linker

Adds tests to ensure that Angular components is compatible with
Angular's patial compilation mode and the linker.

A new job running every hour ensures that changes to the partial
compilation or linker in Angular `master` are compatible with the
components repository. Additionally, we add a job that runs for
each commit/PR in order to insure that Angular components remains
compatible with the linker of already-released Angular versions.

* build: build and run e2e tests in partial compilation mode

* fixup! build: build and run e2e tests in partial compilation mode

Address feedback

)

* fix(material/table): Make table data source interface generic

* fix(material/table): golden api

* fix(material/table): re-export interface

replace ternary operator by if statement with early return
replace redundant forEach statement with neat spread operator

…n import (#22645)

* fix(material-experimental/mdc-slide-toggle): set $deprecated-suffix on import

* build: update to mdc nightly

* ci: fix lint check

* build: update to latest MDC canary

Now that we know that the MDC-based slider won't have the same API as the non-MDC version, we can avoid sharing the test harness tests and clean up some of the logic.

Adds test harnesses for the MDC-based slider components.

…ation (#22658)

Adding support for extra symbols to migrate lets us deal with symbols that we only want to migrate inside Google.

Adds a button that allows us to test noop animations without having to make code changes.

Bumps all of the Angular packages to `rc.3`. Also switches to a stable version of `codelyzer`.

…22643)

Rather than relying on a preinstall script, set `engine-strict` to `true` in a project `.npmrc` file, relying on the `engines` having `npm` set to note that yarn should be used instead