@angular/material 16.2.1 → 17.0.0-next.0

package/legacy-chips/testing/index.d.ts

@@ -1,316 +0,0 @@
-import { BaseHarnessFilters } from '@angular/cdk/testing';
-import { ComponentHarness } from '@angular/cdk/testing';
-import { ContentContainerComponentHarness } from '@angular/cdk/testing';
-import { HarnessPredicate } from '@angular/cdk/testing';
-import { TestKey } from '@angular/cdk/testing';
-
-/**
- * A set of criteria that can be used to filter a list of `MatChipAvatarHarness` instances.
- * @deprecated Use `ChipAvatarHarnessFilters` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare interface LegacyChipAvatarHarnessFilters extends BaseHarnessFilters {
-}
-
-/**
- * A set of criteria that can be used to filter a list of chip instances.
- * @deprecated Use `ChipHarnessFilters` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare interface LegacyChipHarnessFilters extends BaseHarnessFilters {
-    /** Only find instances whose text matches the given value. */
-    text?: string | RegExp;
-    /**
-     * Only find chip instances whose selected state matches the given value.
-     * @deprecated Use Legacy Chip Option Harness together with Legacy Chip Option Harness Filters.
-     * @breaking-change 12.0.0
-     */
-    selected?: boolean;
-}
-
-/**
- * A set of criteria that can be used to filter a list of `MatChipListInputHarness` instances.
- * @deprecated Use `ChipInputHarnessFilters` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare interface LegacyChipInputHarnessFilters extends BaseHarnessFilters {
-    /** Filters based on the value of the input. */
-    value?: string | RegExp;
-    /** Filters based on the placeholder text of the input. */
-    placeholder?: string | RegExp;
-}
-
-/**
- * A set of criteria that can be used to filter selectable chip list instances.
- * @deprecated Use `ChipListboxHarnessFilters` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare interface LegacyChipListboxHarnessFilters extends BaseHarnessFilters {
-}
-
-/**
- * A set of criteria that can be used to filter chip list instances.
- * @deprecated Use `ChipListHarnessFilters` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare interface LegacyChipListHarnessFilters extends BaseHarnessFilters {
-}
-
-/**
- * A set of criteria that can be used to filter a list of selectable chip instances.
- * @deprecated Use `ChipOptionHarnessFilters` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare interface LegacyChipOptionHarnessFilters extends LegacyChipHarnessFilters {
-    /** Only find chip instances whose selected state matches the given value. */
-    selected?: boolean;
-}
-
-/**
- * A set of criteria that can be used to filter a list of `MatChipRemoveHarness` instances.
- * @deprecated Use `ChipRemoveHarnessFilters` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare interface LegacyChipRemoveHarnessFilters extends BaseHarnessFilters {
-}
-
-/**
- * Base class for chip list harnesses.
- * @deprecated Use `class` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-declare abstract class _MatChipListHarnessBase extends ComponentHarness {
-    /** Gets whether the chip list is disabled. */
-    isDisabled(): Promise<boolean>;
-    /** Gets whether the chip list is required. */
-    isRequired(): Promise<boolean>;
-    /** Gets whether the chip list is invalid. */
-    isInvalid(): Promise<boolean>;
-    /** Gets whether the chip list is in multi selection mode. */
-    isMultiple(): Promise<boolean>;
-    /** Gets whether the orientation of the chip list. */
-    getOrientation(): Promise<'horizontal' | 'vertical'>;
-}
-
-/**
- * Harness for interacting with a standard Material chip avatar in tests.
- * @deprecated Use `MatChipAvatarHarness` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-declare class MatLegacyChipAvatarHarness extends ComponentHarness {
-    static hostSelector: string;
-    /**
-     * Gets a `HarnessPredicate` that can be used to search for a `MatChipAvatarHarness` that meets
-     * certain criteria.
-     * @param options Options for filtering which input instances are considered a match.
-     * @return a `HarnessPredicate` configured with the given options.
-     */
-    static with(options?: LegacyChipAvatarHarnessFilters): HarnessPredicate<MatLegacyChipAvatarHarness>;
-}
-
-/**
- * Harness for interacting with a standard selectable Angular Material chip in tests.
- * @deprecated Use `MatChipHarness` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare class MatLegacyChipHarness extends ContentContainerComponentHarness {
-    /** The selector for the host element of a `MatChip` instance. */
-    static hostSelector: string;
-    /**
-     * Gets a `HarnessPredicate` that can be used to search for a `MatChipHarness` that meets
-     * certain criteria.
-     * @param options Options for filtering which chip instances are considered a match.
-     * @return a `HarnessPredicate` configured with the given options.
-     */
-    static with(options?: LegacyChipHarnessFilters): HarnessPredicate<MatLegacyChipHarness>;
-    /** Gets the text of the chip. */
-    getText(): Promise<string>;
-    /**
-     * Whether the chip is selected.
-     * @deprecated Use `MatChipOptionHarness.isSelected` instead.
-     * @breaking-change 12.0.0
-     */
-    isSelected(): Promise<boolean>;
-    /** Whether the chip is disabled. */
-    isDisabled(): Promise<boolean>;
-    /**
-     * Selects the given chip. Only applies if it's selectable.
-     * @deprecated Use `MatChipOptionHarness.select` instead.
-     * @breaking-change 12.0.0
-     */
-    select(): Promise<void>;
-    /**
-     * Deselects the given chip. Only applies if it's selectable.
-     * @deprecated Use `MatChipOptionHarness.deselect` instead.
-     * @breaking-change 12.0.0
-     */
-    deselect(): Promise<void>;
-    /**
-     * Toggles the selected state of the given chip. Only applies if it's selectable.
-     * @deprecated Use `MatChipOptionHarness.toggle` instead.
-     * @breaking-change 12.0.0
-     */
-    toggle(): Promise<void>;
-    /** Removes the given chip. Only applies if it's removable. */
-    remove(): Promise<void>;
-    /**
-     * Gets the remove button inside of a chip.
-     * @param filter Optionally filters which remove buttons are included.
-     */
-    getRemoveButton(filter?: LegacyChipRemoveHarnessFilters): Promise<MatLegacyChipRemoveHarness>;
-    /**
-     * Gets the avatar inside a chip.
-     * @param filter Optionally filters which avatars are included.
-     */
-    getAvatar(filter?: LegacyChipAvatarHarnessFilters): Promise<MatLegacyChipAvatarHarness | null>;
-}
-
-/**
- * Harness for interacting with a standard Material chip inputs in tests.
- * @deprecated Use `MatChipInputHarness` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare class MatLegacyChipInputHarness extends ComponentHarness {
-    static hostSelector: string;
-    /**
-     * Gets a `HarnessPredicate` that can be used to search for a `MatChipInputHarness` that meets
-     * certain criteria.
-     * @param options Options for filtering which input instances are considered a match.
-     * @return a `HarnessPredicate` configured with the given options.
-     */
-    static with(options?: LegacyChipInputHarnessFilters): HarnessPredicate<MatLegacyChipInputHarness>;
-    /** Whether the input is disabled. */
-    isDisabled(): Promise<boolean>;
-    /** Whether the input is required. */
-    isRequired(): Promise<boolean>;
-    /** Gets the value of the input. */
-    getValue(): Promise<string>;
-    /** Gets the placeholder of the input. */
-    getPlaceholder(): Promise<string>;
-    /**
-     * Focuses the input and returns a promise that indicates when the
-     * action is complete.
-     */
-    focus(): Promise<void>;
-    /**
-     * Blurs the input and returns a promise that indicates when the
-     * action is complete.
-     */
-    blur(): Promise<void>;
-    /** Whether the input is focused. */
-    isFocused(): Promise<boolean>;
-    /**
-     * Sets the value of the input. The value will be set by simulating
-     * keypresses that correspond to the given value.
-     */
-    setValue(newValue: string): Promise<void>;
-    /** Sends a chip separator key to the input element. */
-    sendSeparatorKey(key: TestKey | string): Promise<void>;
-}
-
-/**
- * Harness for interacting with a standard selectable chip list in tests.
- * @deprecated Use `MatChipListboxHarness` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare class MatLegacyChipListboxHarness extends _MatChipListHarnessBase {
-    /** The selector for the host element of a `MatChipList` instance. */
-    static hostSelector: string;
-    /**
-     * Gets a `HarnessPredicate` that can be used to search for a `MatChipListHarness` that meets
-     * certain criteria.
-     * @param options Options for filtering which chip list instances are considered a match.
-     * @return a `HarnessPredicate` configured with the given options.
-     */
-    static with(options?: LegacyChipListboxHarnessFilters): HarnessPredicate<MatLegacyChipListboxHarness>;
-    /**
-     * Gets the list of chips inside the chip list.
-     * @param filter Optionally filters which chips are included.
-     */
-    getChips(filter?: LegacyChipOptionHarnessFilters): Promise<MatLegacyChipOptionHarness[]>;
-    /**
-     * Selects a chip inside the chip list.
-     * @param filter An optional filter to apply to the child chips.
-     *    All the chips matching the filter will be selected.
-     */
-    selectChips(filter?: LegacyChipOptionHarnessFilters): Promise<void>;
-}
-
-/**
- * Harness for interacting with a standard chip list in tests.
- * @deprecated Use `MatChipListHarness` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare class MatLegacyChipListHarness extends _MatChipListHarnessBase {
-    /** The selector for the host element of a `MatChipList` instance. */
-    static hostSelector: string;
-    /**
-     * Gets a `HarnessPredicate` that can be used to search for a `MatChipListHarness` that meets
-     * certain criteria.
-     * @param options Options for filtering which chip list instances are considered a match.
-     * @return a `HarnessPredicate` configured with the given options.
-     */
-    static with(options?: LegacyChipListHarnessFilters): HarnessPredicate<MatLegacyChipListHarness>;
-    /**
-     * Gets the list of chips inside the chip list.
-     * @param filter Optionally filters which chips are included.
-     */
-    getChips(filter?: LegacyChipHarnessFilters): Promise<MatLegacyChipHarness[]>;
-    /**
-     * Selects a chip inside the chip list.
-     * @param filter An optional filter to apply to the child chips.
-     *    All the chips matching the filter will be selected.
-     * @deprecated Use `MatChipListboxHarness.selectChips` instead.
-     * @breaking-change 12.0.0
-     */
-    selectChips(filter?: LegacyChipHarnessFilters): Promise<void>;
-    /**
-     * Gets the `MatChipInput` inside the chip list.
-     * @param filter Optionally filters which chip input is included.
-     */
-    getInput(filter?: LegacyChipInputHarnessFilters): Promise<MatLegacyChipInputHarness>;
-}
-
-/**
- * @deprecated Use `MatChipOptionHarness` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare class MatLegacyChipOptionHarness extends MatLegacyChipHarness {
-    /** The selector for the host element of a selectable chip instance. */
-    static hostSelector: string;
-    /**
-     * Gets a `HarnessPredicate` that can be used to search for a `MatChipOptionHarness`
-     * that meets certain criteria.
-     * @param options Options for filtering which chip instances are considered a match.
-     * @return a `HarnessPredicate` configured with the given options.
-     */
-    static with(options?: LegacyChipOptionHarnessFilters): HarnessPredicate<MatLegacyChipOptionHarness>;
-    /** Whether the chip is selected. */
-    isSelected(): Promise<boolean>;
-    /** Selects the given chip. Only applies if it's selectable. */
-    select(): Promise<void>;
-    /** Deselects the given chip. Only applies if it's selectable. */
-    deselect(): Promise<void>;
-    /** Toggles the selected state of the given chip. */
-    toggle(): Promise<void>;
-}
-
-/**
- * Harness for interacting with a standard Material chip remove button in tests.
- * @deprecated Use `MatChipRemoveHarness` from `@angular/material/chips/testing` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
- * @breaking-change 17.0.0
- */
-export declare class MatLegacyChipRemoveHarness extends ComponentHarness {
-    static hostSelector: string;
-    /**
-     * Gets a `HarnessPredicate` that can be used to search for a `MatChipRemoveHarness` that meets
-     * certain criteria.
-     * @param options Options for filtering which input instances are considered a match.
-     * @return a `HarnessPredicate` configured with the given options.
-     */
-    static with(options?: LegacyChipRemoveHarnessFilters): HarnessPredicate<MatLegacyChipRemoveHarness>;
-    /** Clicks the remove button. */
-    click(): Promise<void>;
-}
-
-export { }

package/legacy-core/_core-theme.scss

@@ -1,65 +0,0 @@
-@use 'sass:map';
-@use '../core/theming/theming';
-@use '../core/ripple/ripple-theme';
-@use '../core/selection/pseudo-checkbox/pseudo-checkbox-theme';
-@use './option/option-theme';
-@use './option/optgroup-theme';
-@use '../core/style/elevation';
-@use '../core/style/private';
-
-/// @deprecated Use `mat.core-color` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
-/// @breaking-change 17.0.0
-@mixin color($config-or-theme) {
-  $config: theming.get-color-config($config-or-theme);
-
-  // Wrapper element that provides the theme background when the user's content isn't
-  // inside of a `mat-sidenav-container`. Note that we need to exclude the ampersand
-  // selector in case the mixin is included at the top level.
-  .mat-app-background#{if(&, ', &.mat-app-background', '')} {
-    $background: map.get($config, background);
-    $foreground: map.get($config, foreground);
-
-    background-color: theming.get-color-from-palette($background, background);
-    color: theming.get-color-from-palette($foreground, text);
-  }
-
-  // Provides external CSS classes for each elevation value. Each CSS class is formatted as
-  // `mat-elevation-z$zValue` where `$zValue` corresponds to the z-space to which the element is
-  // elevated.
-  @for $zValue from 0 through 24 {
-    .#{elevation.$prefix}#{$zValue} {
-      @include private.private-theme-elevation($zValue, $config);
-    }
-  }
-
-  // Marker that is used to determine whether the user has added a theme to their page.
-  @at-root {
-    .mat-theme-loaded-marker {
-      display: none;
-    }
-  }
-}
-
-// Mixin that renders all of the core styles that depend on the theme.
-/// @deprecated Use `mat.core-theme` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
-/// @breaking-change 17.0.0
-@mixin theme($theme-or-color-config) {
-  $theme: theming.private-legacy-get-theme($theme-or-color-config);
-  // Wrap the sub-theme includes in the duplicate theme styles mixin. This ensures that
-  // there won't be multiple warnings. e.g. if `mat-core-theme` reports a warning, then
-  // the imported themes (such as `mat-ripple-theme`) should not report again.
-  @include theming.private-check-duplicate-theme-styles($theme, 'mat-legacy-core') {
-    // Legacy-specific themes.
-    @include option-theme.theme($theme);
-    @include optgroup-theme.theme($theme);
-
-    // Non-legacy themes that are forwarded.
-    @include ripple-theme.theme($theme);
-    @include pseudo-checkbox-theme.theme($theme);
-
-    $color: theming.get-color-config($theme);
-    @if $color != null {
-      @include color($color);
-    }
-  }
-}

package/legacy-core/_core.import.scss

@@ -1,5 +0,0 @@
-@forward 'core' hide core;
-@forward 'core' as mat-legacy-*;
-@forward 'core' as mat-legacy-core-legacy-*;
-
-@import './typography/all-typography';

package/legacy-core/_core.scss

@@ -1,18 +0,0 @@
-@use '@angular/cdk';
-
-// Core styles that can be used to apply material design treatments to any element.
-@use '../core/ripple/ripple';
-@use '../core/focus-indicators/private';
-
-// Mixin that renders all of the core styles that are not theme-dependent.
-/// @deprecated Use `mat.core` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
-/// @breaking-change 17.0.0
-@mixin core() {
-  @include ripple.ripple();
-  @include cdk.a11y-visually-hidden();
-  @include cdk.overlay();
-  @include cdk.text-field-autosize();
-  @include cdk.text-field-autofill();
-  @include private.structural-styling('mat');
-  @include private.structural-styling('mat-mdc');
-}

package/legacy-core/color/_all-color.import.scss

@@ -1,4 +0,0 @@
-@forward 'all-color';
-
-@import '../theming/all-theme';
-@import '../../core/theming/theming';

package/legacy-core/color/_all-color.scss

@@ -1,28 +0,0 @@
-@use '../theming/all-theme';
-@use '../../core/theming/theming';
-
-// Includes all of the color styles.
-/// @deprecated Use `mat.all-component-colors` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
-/// @breaking-change 17.0.0
-@mixin all-legacy-component-colors($config-or-theme) {
-  // In case a theme object has been passed instead of a configuration for
-  // the color system, extract the color config from the theme object.
-  $config: if(theming.private-is-theme-object($config-or-theme),
-      theming.get-color-config($config-or-theme), $config-or-theme);
-
-  @if $config == null {
-    @error 'No color configuration specified.';
-  }
-
-  @include all-theme.all-legacy-component-themes((
-    color: $config,
-    typography: null,
-    density: null,
-  ));
-}
-
-/// @deprecated Use `mat.all-component-colors` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
-/// @breaking-change 17.0.0
-@mixin angular-material-legacy-color($config-or-theme) {
-  @include all-legacy-component-colors($config-or-theme);
-}

package/legacy-core/density/private/_all-density.import.scss

@@ -1,3 +0,0 @@
-@forward 'all-density' hide all-legacy-component-densities;
-
-@import '../../../core/theming/theming';

package/legacy-core/density/private/_all-density.scss

@@ -1,46 +0,0 @@
-@use '../../../core/theming/theming';
-@use '../../../legacy-form-field/form-field-theme';
-@use '../../../expansion/expansion-theme';
-@use '../../../stepper/stepper-theme';
-@use '../../../toolbar/toolbar-theme';
-@use '../../../tree/tree-theme';
-@use '../../../button-toggle/button-toggle-theme';
-
-// Add legacy theme imports here, e.g.:
-// @use '../../../<legacy-component>/<legacy-component>-theme';
-
-// Includes all of the density styles.
-/// @deprecated Use `mat.all-component-densities` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
-/// @breaking-change 17.0.0
-@mixin all-legacy-component-densities($config-or-theme) {
-  // In case a theme object has been passed instead of a configuration for
-  // the density system, extract the density config from the theme object.
-  $config: if(theming.private-is-theme-object($config-or-theme),
-      theming.get-density-config($config-or-theme), $config-or-theme);
-
-  @if $config == null {
-    @error 'No density configuration specified.';
-  }
-
-  // TODO: COMP-309: Do not use individual mixins. Instead, use the all-theme mixin and only
-  // specify a `density` config while setting `color` and `typography` to `null`. This is currently
-  // not possible as it would introduce a circular dependency for density because the `mat-core`
-  // mixin that is transitively loaded by the `all-theme` file, imports `all-density` which
-  // would then load `all-theme` again. This ultimately results a circular dependency.
-
-  // Add legacy density includes here, e.g.:
-  // @include <legacy-component>-theme.density($config);
-  @include form-field-theme.density($config);
-  @include expansion-theme.density($config);
-  @include stepper-theme.density($config);
-  @include toolbar-theme.density($config);
-  @include tree-theme.density($config);
-  @include button-toggle-theme.density($config);
-}
-
-
-/// @deprecated Use `mat.all-component-densities` instead. See https://material.angular.io/guide/mdc-migration for information about migrating.
-/// @breaking-change 17.0.0
-@mixin angular-material-legacy-density($config-or-theme) {
-  @include all-legacy-component-densities($config-or-theme);
-}

package/legacy-core/density/private/_compatibility.import.scss

@@ -1,4 +0,0 @@
-@forward 'compatibility' hide $private-density-generate-at-root, $private-density-generate-styles,
-private-density-legacy-compatibility, private-density-prop-value;
-@forward 'compatibility' as mat-* hide $mat-default-scale, $mat-interval, $mat-maximum-scale,
-$mat-minimum-scale, $mat-supported-scales;

package/legacy-core/density/private/_compatibility.scss

@@ -1,74 +0,0 @@
-@use 'sass:list';
-@use 'sass:map';
-@use 'sass:meta';
-// Note that this file is called `private`, because the APIs in it aren't public yet.
-// Once they're made available, the code should be moved out into an `index.scss`.
-
-// Taken from mat-density with small modifications to not rely on the new Sass module
-// system, and to support arbitrary properties in a density configuration.
-// https://github.com/material-components/material-components-web/blob/master/packages/mdc-density
-
-$_density-interval: 4px !default;
-$_minimum-scale: minimum !default;
-$_maximum-scale: maximum !default;
-$_supported-scales: (default, $_minimum-scale, $_maximum-scale) !default;
-$_default-scale: 0 !default;
-
-// Whether density should be generated at root. This will be temporarily set to `true`
-// whenever density styles for legacy themes are generated.
-$private-density-generate-at-root: false;
-// Whether density styles should be generated. This will be temporarily set to `false` if
-// duplicate density styles for a legacy theme would be generated. For legacy themes,
-// we always generate the default density **only once** at root.
-$private-density-generate-styles: true;
-
-// Mixin that can be used to wrap density styles of given components. The mixin will
-// move the density styles to root if the `$mat-private-density-generate-at-root` global variable
-// is set. If `$mat-private-density-generate-styles` is set to `false`, generation of density
-// styles wrapped in this mixin is skipped. This mixin exists to improve backwards compatibility
-// of the new theming API where density styles are included as part of themes. Previously,
-// density styles of components were part of their base styles. With the new API, they are
-// part of the theming system. The `<..>-theme` mixins generate density by default unless
-// the density configuration is explicitly specified as per new API. This means, that projects
-// using `<..>-theme` mixins for separate themes (like `.dark-theme`) will cause duplicate
-// density styles. This is breaking as it increases specificity of density styles. This mixin
-// provides an API to control generation of density styles so that we can ensure they are only
-// created *once* and at root.
-@mixin private-density-legacy-compatibility() {
-  @if $private-density-generate-styles and $private-density-generate-at-root {
-    @at-root {
-      @content;
-    }
-  }
-  @else if $private-density-generate-styles {
-    @content;
-  }
-}
-
-@function private-density-prop-value($density-config, $density-scale, $property-name) {
-  @if (meta.type-of($density-scale) == 'string' and
-      list.index($list: $_supported-scales, $value: $density-scale) == null) {
-    @error 'mat-density: Supported density scales #{$_supported-scales}, '  +
-      'but received #{$density-scale}.';
-  }
-
-  $value: null;
-  $property-scale-map: map.get($density-config, $property-name);
-
-  @if map.has-key($property-scale-map, $density-scale) {
-    $value: map.get($property-scale-map, $density-scale);
-  }
-  @else {
-    $value: map.get($property-scale-map, default) + $density-scale * $_density-interval;
-  }
-
-  $min-value: map.get($property-scale-map, $_minimum-scale);
-  $max-value: map.get($property-scale-map, $_maximum-scale);
-
-  @if ($value < $min-value or $value > $max-value) {
-    @error 'mat-density: #{$property-name} must be between #{$min-value} and ' +
-      '#{$max-value} (inclusive), but received #{$value}.';
-  }
-
-  @return $value;
-}