Paul Gschwendtner

Seems like a reasonable feature request to me. Apparently, the form-field follows the Material Design spec, so adding such flexibility for custom styling could be considered out of scope, but...

that would be great, thanks

That might be somewhat similar to https://github.com/angular/components/issues/17037.

@DwieDima Aren't these things currently all configurable as we don't load the Google Maps API automatically? So it's actually the responsibility of actual consumers of the `google-maps` package. Is this...

@DwieDima Thanks for the quick response. Could you help providing a small example of styles you are referring to? My thinking is that apiKey, language, region etc. are configurable when...

Thanks for clarifying. So I think there are two parts you're requesting: 1. Global options for the API loading mechanism. That would also involve us automatically loading the google-maps API...

This is actually an intentional duplication to ensure backwards compatibility since we changed some of the internals of the theming API in preparation for density with MDC etc. We should...

Just capturing this here: https://github.com/angular/components/pull/24835. In V15/V16 we will remove this.

@crisbeto Did we explicitly deprecate the `.import` and legacy theming entry-point or can we just consider this being part of the PR above?

This can happen when Microsoft API extractor prints to stdout and conflicts with the Bazel worker IPC also using stdout. Potentially there are some warnings with type bundling. You can...