lightning-base-components 1.27.2-alpha → 1.28.3-alpha

package/src/lightning/input/__requirements__/requirements.md

@@ -1,98 +0,0 @@
-### Events
-
-- When entering a value and that value is "committed", a 'commit' event is dispatch, the event is not bubbling,
-  nor cancelable and has no detail.
-  Committing a number is defined as:
-  the user presses Enter
-  OR blurs away from the input
-  OR presses the "x" clear button for type search)
-
-### `number``
-
-- When not a valid ISO number is passed as a value to the input
-  either via an attribute `<lightning-input type="number" value="notANumber"` or
-  property `component.value = 'notANumber'`, the value should be set to empty string.
-  This also means on type changes the number needs to be re-parsed.
-
-    > Covered by Jest tests.
-
-- When not a valid ISO number is passed to 'step', the value of the step should be the default one.
-  Currently that default is 'undefined'. It would be better if this value would be '1' instead.
-
-    > Covered by Jest tests.
-
-- When entering a number, as the number is typed, it's converted to an ISO number and set as the value.
-  The conversion is done by using the user's current locale (not browser and not OS but rather the locale provided
-  by the localization service).
-
-    > Covered by integration tests
-
-- In mobile environments a "numbers" keyboard should be presented when an input of type number is tapped.
-  This is done by setting `inputmode="decimal"`
-
-    > Covered by snapshot test
-
-- When input has the focus and Up/Down key arrows are pressed, the number is increased/decreased as by the given step, if step is not given, the increases are by 1 and the number is rounded off to an integer.
-  When no initial number is given a value of 0 is used (as such a clck on '-' would net -1, and and '+" would result in 1).
-
-    > Covered by integration tests
-
-- When numbers are increased either via Up/Down keys or by pressing the - and + buttons, both 'commit' and 'change'
-  events are dispatched.
-
-- Bad input (like 1eee3) is flagged as invalid, when an input is flagged as invalid the input should not be formatted
-  when blurred, the original input is kept.
-
-    > Covered by integration tests
-
-- Entering West-Arabic/Hindu numbers should be supported. Due to the way aura localisation implements this these numbers
-  can be mixed with regular numbers and can be entered even if the user locale is not of those types.
-
-- Very long number input should be supported (the number is no longer rounded off). This is subject to precision
-  limitation of the Up/Down increase/decrease and various operations (like max/min/step checks which are still bound by the usual js limits)
-
-    > Covered by integration Tests
-
-- The 'change' event is fired when the component transitions to a badInput state (ie. validity.badInput is true).
-  Specifically if a valid value is entered followed by a character that's invalid, it will trigger a 'change' event, and
-  the value will be ''.
-
-    > Covered by integration tests
-
-- When a number starts with a decimal separator (like -.2 or .3), the resulting value should always have a zero
-  in front (ie. .value should be -0.2 and 0.3 respectively)
-
-    > Covered by Jest tests
-
-- 'step' attribute is used to determine the significant digits for formatting of a number; when 'step' has a superfluous .0 at the end, the number of significant digits should be 0; exponent format should also be correctly calculated, eg. 1.5e-5 should net 6 significant digits when formatting the number; positive exponents should also be correctly parsed (eg. 1e10 should net 0)
-
-    > Covered by Jest tests
-
-- only valid characters are allowed to be typed (anything can be pasted in however), valid characters are considered:
-    - `0-9`
-    - `k` `K` `m` `M` `b` `B` `t` `T` (shortcuts)
-    - `e` `E` (exponent)
-    - `+` `-` `.` `,`
-    - West-Arabic/Hindu numbers
-        > Covered by Jest and integration tests
-
-#### number 'k' / 'm' / 'b' shortcuts
-
-- When an entered valid number in the given locale ends in "k", "K", "m", "M", "b", "B", "t" or "T" (shortcut suffix):
-    - as soon as the suffix is entered `value` is `1000 * the entered` number if "k" or "K" is the suffix, or `1000000 * the entered number` if "m" or "M" is the suffix, or `1000000000 * the entered number` if "b" or "B" is the suffix, or `1000000000000 * the entered number` if "t" or "T" is the suffix
-        > Covered by Jest and Integration tests
-    - when blurring from the input, the value shown on the input should reflect the multiplied number (eg. for `1k` it could be `1,000` for a locale with `,` as a grouping separator)
-        > Covered by Jest and Integration tests
-    - when the input is focused, the value that's in the input will be the multiplied number
-      in the given locale with the correct decimal separator and no grouping separators (eg. if in a locale with "," as a decimal separator number `0,0001k` was entered, when focusing after a blur the number should show as `0,1`)
-        > Covered by Jest and Integration tests (partially, it would be good to have a test that overrides the locale used to test with locales that have different decimal digits)
-- If the input is not a valid number but has a shortcut suffix at the end, when blurring from the input, and then focusing back on it, the original entered string should be preserved (eg. if `100eee10k` is entered, blurring out and focusing should preserve that value)
-    > Covered by Jest tests
-- When setting the value programmatically, value that contains a shortcut suffix should not be considered valid
-    > Covered by Jest tests
-
-### Open questions
-
-- We need to define the behaviour for - and + when max or min are hit, and also whether it should round to the
-  closest step. In addition the behaviour for when the number is larger than what js arithmetics can handle (because
-  of the rounding errors the increase/decrease does nothing).

package/src/lightning/input/input.js-meta.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<LightningComponentBundle xmlns="xmlns=http://soap.sforce.com/2006/04/metadata">
-    <isExposed>true</isExposed>
-    <minApiVersion>0.0</minApiVersion>
-    <support>GA</support>
-    <capabilities>
-        <capability>lightning__ServerRenderableWithHydration</capability>
-    </capabilities>
-</LightningComponentBundle>

package/src/lightning/inputAddress/__docs__/inputAddress.md

@@ -1,470 +0,0 @@
----
-examples:
-    - name: base
-      label: Basic Address Input
-      description: Address fields can be prepopulated and marked as required.
-    - name: stateAndCountryPicklists
-      label: Address With State and Country Picklists
-      description: Address fields support predefined lists of states and countries.
-    - name: customLocale
-      label: Address With Custom Locale
-      description: Address input fields ordered depending on custom locale value.
----
-
-A `lightning-input-address` component creates a compound field that includes the following constituent fields.
-
-- Street
-- City
-- Province
-- Country
-- Postal code
-
-The street field is displayed as a multi-line text field. The other fields are displayed as a text input field by default. The country and province fields are displayed as dropdown menus if you specify `country-options` and `province-options` to provide options for menu items.
-
-This example creates an address compound field with attributes to specify values for the constituent fields. The initial values are set directly with the attributes.
-
-```html
-<template>
-    <div>
-        <lightning-input-address
-            address-label="Address"
-            street-label="Street"
-            city-label="City"
-            country-label="Country"
-            province-label="State"
-            postal-code-label="PostalCode"
-            street="1 Market St."
-            city="San Francisco"
-            country="US"
-            province="CA"
-            postal-code="94105"
-            field-level-help="Enter your billing address"
-        >
-        </lightning-input-address>
-    </div>
-</template>
-```
-
-`lightning-input-address` uses the `onchange` event handler to listen to a change to its field values.
-
-```html
-<p>You are located in: {city}</p>
-    <lightning-input-address
-        address-label="Address"
-        street-label="Street"
-        city-label="City"
-        country-label="Country"
-        province-label="Province"
-        postal-code-label="PostalCode"
-        city={city}
-        onchange={handleChange} ></lightning-input-address>
-```
-
-To bind the input value on the address fields, use the `event.target` property.
-
-```js
-import { LightningElement } from 'lwc';
-
-export default class AddressCityExample extends LightningElement {
-    city = "San Francisco";
-
-    handleChange(event) {
-        this.city = event.target.city;
-    }
-}
-```
-
-See the **Custom Events** section for a list of `event.target` properties. For more information, see [Data Binding in a Template](https://developer.salesforce.com/docs/platform/lwc/guide/js-props-getter).
-
-#### Creating Dropdown Menus for Country and Province
-
-To create a dropdown menu for the country and province, pass in an array of
-label-value pairs to `country-options` and `province-options`. Use the `country` and
-`province` attributes to specify the default values on the dropdown menus.
-
-```html
-<template>
-    <div>
-        <lightning-input-address
-            address-label="Address"
-            street-label="Street"
-            city-label="City"
-            country-label="Country"
-            province-label="Province/State"
-            postal-code-label="PostalCode"
-            street="1 Market St."
-            city="San Francisco"
-            province="CA"
-            country="US"
-            country-options={getCountryOptions}
-            province-options={getProvinceOptions}
-            postal-code="94105"
-            required
-            onchange={handleChange}
-        >
-        </lightning-input-address>
-    </div>
-</template>
-```
-
-JavaScript file:
-
-```javascript
-import { LightningElement } from 'lwc';
-
-export default class DemoInputAddress extends LightningElement {
-    provinceOptions = [
-        { label: 'California', value: 'CA' },
-        { label: 'Texas', value: 'TX' },
-        { label: 'Washington', value: 'WA' },
-    ];
-
-    countryOptions = [
-        { label: 'United States', value: 'US' },
-        { label: 'Japan', value: 'JP' },
-        { label: 'China', value: 'CN' },
-    ];
-
-    get getProvinceOptions() {
-        return this.countryProvinceMap[this._country];
-    }
-    get getCountryOptions() {
-        return this.countryOptions;
-    }
-
-    handleChange(event) {
-        this._country = event.detail.country;
-    }
-}
-```
-
-Alternatively, you can enable state and country picklists in your org, and
-access the values by using a wire adapter.
-See [Let Users Select State and Country from Picklists](https://help.salesforce.com/articleView?id=admin_state_country_picklists_overview.htm) in Salesforce Help and [getPicklistValues](https://developer.salesforce.com/docs/platform/lwc/guide/reference-wire-adapters-picklist-values) in the Lightning Web Components Developer Guide.
-
-#### Using the Locale Information
-
-In Lightning Experience, the `locale` value corresponds to the **Locale** field on the Language &amp; Time Zone page in the user's settings. For example, if you select "French (France)" in the **Locale** field, `lightning-input-address` uses `fr-FR` as the locale.
-
-To override the locale on your user's settings, provide your own `locale` value.
-
-```html
-<template>
-    <div class="slds-var-m-around_medium">
-        <h2>User's locale: {userLocale}</h2>
-        <lightning-input-address
-            address-label="Address"
-            street-label="Street"
-            city-label="City"
-            country-label="Country"
-            province-label="Province"
-            postal-code-label="Postal Code"
-            locale="en-US"></lightning-input-address>
-    </div>
-</template>
-```
-
-In this example, the `userLocale` property returns `fr-FR` and the `lightning-input-address` component uses the `en-US` locale.
-
-```javascript
-import { LightningElement } from 'lwc';
-import LOCALE from '@salesforce/i18n/locale';
-
-export default class LocaleExample extends LightningElement {
-
-    userLocale = LOCALE;
-}
-
-```
-
-If you pass in an invalid locale, the component uses `en-US`.
-
-For more information, see [Access Internationalization Properties](https://developer.salesforce.com/docs/platform/lwc/guide/create-i18n.html) in the Lightning Web Components Dev Guide.
-
-#### Hiding the Province Field
-
-The province field is used with countries that include a province in their addresses. This field can also be used as a field for state information, such as in United States addresses.
-
-To visually hide the province field from the component's fields layout for locales that don't require it, use the `hide-province` attribute. For example, you can use `hide-province` when the `locale` is `fr-FR` or `zh-CN`.
-
-```html
-<template>
-     <lightning-input-address
-        address-label="Address"
-        street-label="Street"
-        city-label="City"
-        country-label="Country"
-        province-label="Province"
-        postal-code-label="Postal Code"
-        locale="fr-FR"
-        hide-province
-    ></lightning-input-address>
-</template>
-```
-
-If you don't provide a value for `province-label`, the component renders with a province field without a label. Hide the field using `hide-province`.
-
-#### Using Lookup to Find and Autofill an Address
-
-To enable autocompletion of the address fields using an address lookup field, include the `show-address-lookup` attribute. The address lookup field is placed above the address fields you provide.
-
-```html
-<template>
-    <lightning-input-address
-        show-address-lookup
-        address-label="Address"
-        street-label="Street"
-        city-label="City"
-        country-label="Country"
-        province-label="State"
-        postal-code-label="Zip Code"
-        street="1 Market St."
-        city="San Francisco"
-        country="US"
-        province="CA"
-    >
-    </lightning-input-address>
-</template>
-```
-
-When you start typing an address in the lookup field, a dropdown menu displays matching addresses returned by the Google Maps Places API. Select an address from the dropdown to populate the address fields.
-
-#### Filter Address Lookup Based on Country Options
-
-To filter address lookups by country, pass in an array of ISO 3166-1 Alpha-2 country code strings to the `country-lookup-filter` attribute. Country codes are case-insensitive. Enable address lookup by including `show-address-lookup`.
-
-```html
-<template>
-    <lightning-input-address
-        show-address-lookup
-        address-label="Address"
-        street-label="Street"
-        city-label="City"
-        province-label="State"
-        country-label="Country"
-        postal-code-label="Zip Code"
-        country-lookup-filter={countries}
-    >
-    </lightning-input-address>
-</template>
-```
-
-In your JavaScript file, pass in a list of country codes. You can specify a maximum of five country codes.
-
-```javascript
-import { LightningElement } from 'lwc';
-
-export default class CountryFilterExample extends LightningElement {
-  countries = ['AU', 'GB', 'JP']; 
-}
-```
-
-For a list of valid country codes, see [Google for Developers: countries.csv](https://developers.google.com/public-data/docs/canonical/countries_csv).
-
-**Important:** Using an invalid two-letter country code in the array prevents the Google Maps Places API from returning results and may trigger console errors. If the array contains a country code longer than two characters or exceeds the five-country filter limit, the component defaults to using no filter. Additionally, if a non-array value is passed to the attribute, the component also defaults to using no filter.
-
-Using `show-address-lookup` is not supported in Experience Builder sites, Lightning Out,
-Lightning Components for Visualforce, and standalone apps. While it may work, these targets are not optimized and not officially supported.
-
-#### Using Compact Address Fields
-
-By default, the Street address field is a textarea field. Use compact address fields if you want to separate the Street address field into two input fields instead.
-
-To display compact address fields, include the `show-compact-address` attribute. Use `street-label` to provide a label for the first line of address, and use `subpremise-label` for the second line of address. You can add supplementary information on this field, such as a building number or unit name.
-
-```html
-<lightning-input-address
-    show-compact-address
-    address-label="Address"
-    street-label="Street Line 1"
-    subpremise-label="Street Line 2"
-    city-label="City"
-    country-label="Country"
-    province-label="Province"
-    postal-code-label="Postal Code"></lightning-input-address>
-```
-
-#### Using the Compact Address Fields with Address Lookup
-
-To enable compact address fields with address lookup, include the `show-address-lookup` and `show-compact-address` attributes. These attributes enable the first street address field as a lookup field.
-
-```html
-<lightning-input-address
-    show-address-lookup
-    show-compact-address
-    address-label="Address"
-    street-label="Street Line 1"
-    city-label="City"
-    country-label="Country"
-    province-label="Province"
-    postal-code-label="Postal Code"></lightning-input-address>
-```
-
-When you start typing an address in the lookup field, a dropdown menu displays matching addresses returned by the Google Maps Places API. Select an address from the dropdown to populate the address fields.
-
-#### Using the Subpremise Field with Address Lookup
-
-Subpremise information includes apartment, unit, or floor number. To provide a label on the subpremise field, use the `subpremise-label` attribute. The second address field is used as the subpremise field.
-
-You can provide a subpremise value using the `subpremise` attribute. The first input field continues to use `street-label`. The `subpremise` field doesn't require a value for submission.
-
-```html
-<lightning-input-address
-    show-address-lookup
-    show-compact-address
-    address-label="Address"
-    street-label="Street Line 1"
-    subpremise-label="Street Line 2"
-    city-label="City"
-    country-label="Country"
-    province-label="Province"
-    postal-code-label="Postal Code"></lightning-input-address>
-```
-
-Google Maps API currently supports subpremises for Australia, New Zealand, and Canada only. The placement of subpremise information is different for each country. For example, Australian addresses include the subpremise information as a prefix to street number, such as `2/1 Tully Road` where `2` is the subpremise. When you enter this address and select it from the search results, the street field is populated with the subpremise and street information while the subpremise field remains empty.
-
-Populating the subpremise field using address lookup isn't currently supported. For example, US addresses include the subpremise after the street number, such as `123 Main St, Unit 10`. When you enter the address with a subpremise, the subpremise appears with the street address in the result list. However, selecting the address from the search result doesn't populate the subpremise field. The street field also doesn't preserve the subpremise, but you can enter it manually in the street or subpremise field.
-
-#### Validating Required Fields
-
-When you set `required`, a red asterisk is displayed on every address
-field to indicate that an entry in each field is required. An error message is displayed below
-a field if a user interacted with it and left it blank. The `required`
-attribute is not enforced and you must validate it before submitting a form
-that contains an address compound field.
-
-Let's say you have a `lightning-button` component that calls the `handleClick`
-function. You can display the error message when a user clicks the
-button without providing a value on a field.
-
-```javascript
-    handleClick(e) {
-        const address =
-            this.template.querySelector('lightning-input-address');
-        const isValid = address.checkValidity();
-        if(isValid) {
-            alert("Creating a new address");
-        } else {
-            alert("Complete all address fields");
-        }
-    }
-```
-
-#### Working with Labels and Placeholders
-
-A label is associated with an address field and it enables screen readers to navigate the form correctly. Include a label for each field you're using, with the following attributes.
-
-- `address-label`
-- `street-label`
-- `city-label`
-- `province-label`
-- `country-label`
-- `postal-code-label`
-
-You can hide the `address-label` visually and still make them accessible to screen readers by using `variant="label-hidden"`.
-
-Additionally, the `show-address-lookup` boolean attribute creates a search field that doesn't have an associated label. See **Using Lookup to Find and Autofill an Address** for more information.
-
-Your Salesforce locale setting determines the order and layout of the input address fields by default. Use the `locale` attribute to override the default. Specify any locale code from the list of [Supported Number, Name, and Address Formats (ICU)](https://help.salesforce.com/s/articleView?id=sf.admin_supported_locales.htm&type=5").
-
-You can also use custom labels that display translated values. For more information, see
-[Access Labels](https://developer.salesforce.com/docs/platform/lwc/guide/create-labels).
-
-We recommend that you provide a label even when you provide placeholder text for an address field. Without field labels, users can lose context when the placeholder text disappears as they type in the field.
-
-Specify placeholder text to give users a hint about the content they're expected to enter in the field. Avoid repeating the field label in the placeholder for better accessibility. Consider the width of your address field as the placeholder text is cut off if it's too long, especially on mobile devices.
-
-Include an optional placeholder for each field you're using, with the following attributes.
-
-- `address-lookup-placeholder`
-- `street-placeholder`
-- `city-placeholder`
-- `province-placeholder`
-- `country-placeholder`
-- `postal-code-placeholder`
-
-#### Component Styling
-
-`lightning-input-address` implements the
-[form element](https://lightningdesignsystem.com/components/form-element/#Address) address blueprint in the
-Salesforce Lightning Design System (SLDS).
-
-You can use a combination of the `variant` and `class` attributes to customize the address fields.
-
-##### Variants
-
-Use the `variant` attribute with one of these values to apply different label positioning.
-
-- `label-hidden` hides the compound field label but make it available to assistive technology. This variant does not hide the constituent field labels.
-- `label-inline` horizontally aligns the compound field label and address fields.
-- `label-stacked` places the label above the address fields.
-- `standard` is the default value, which displays the label above the address fields.
-
-##### Customize Component Styling
-
-To apply additional styling, use the SLDS [utility classes](https://www.lightningdesignsystem.com/utilities/alignment) with the `class` attribute.
-
-This example adds padding on top of address fields using an SLDS class.
-
-```html
-<lightning-input-address
-    class="slds-p-top_small"
-    address-label="Address"
-    street-label="Street"
-    city-label="City"
-    country-label="Country"
-    province-label="Province"
-    postal-code-label="PostalCode"
->
-</lightning-input-address>
-```
-
-The Street field renders a [textarea](https://www.lightningdesignsystem.com/components/textarea) and the other fields render [input](https://www.lightningdesignsystem.com/components/input/) fields.
-
-Component styling hooks use the `--slds-c-*` prefix and change styling for specific elements or properties of a component. Component-specific styling isn’t recommended, because it’s unsupported for SLDS 2, but existing customizations still work with the original SLDS. If you use component styling hooks, limit the components to SLDS themes until SLDS 2 and the Salesforce Cosmos theme become generally available. See [Input: Styling Hooks Overview](https://www.lightningdesignsystem.com/components/input/#Styling-Hooks-Overview) and [Textarea: Styling Hooks Overview](https://www.lightningdesignsystem.com/components/textarea/#CSS-Class-Overview) for documentation on component-specific hooks for this component.
-
-#### Usage Considerations
-
-Using `show-address-lookup` is not supported in Experience Builder sites, Lightning Out,
-Lightning Components for Visualforce, and standalone apps.
-
-When working with address fields such as with the `MailingAddress` field on Salesforce records, consider using the record form components. The `lightning-record-form`, `lightning-record-view-form`, and `lightning-record-edit-form` components provide a form-based UI that's metadata-driven. The components are automatically wired up to your record data, labels, and field-level help text. For more information, see [Work with Records Using Base Components](https://developer.salesforce.com/docs/platform/lwc/guide/data-get-user-input-intro).
-
-To create your own custom UI to work with Salesforce records, use `lightning-input-address` with the `lightning/ui*Api` wire adapters and functions, such as `getRecord` and `updateRecord`. For more information, see [Use the Wire Service with Base Components](https://developer.salesforce.com/docs/platform/lwc/guide/data-wire-base-components).
-
-To disable the fields so that users cannot interact with it, use the `disabled` attribute. If you want to prevent users from interacting with the country field only,
-disable it using the `country-disabled` attribute.
-
-#### Accessibility
-
-You must provide a text label for accessibility to make the information available to assistive technology.
-The `label` attribute creates an HTML `<label>` element for your address.
-To hide the compound field label from view and make it available to assistive technology, use the `label-hidden` variant.
-This variant keeps the constituent field labels in view.
-
-This component uses `button` elements for picklists to comply with the [Lightning Design System combobox blueprint](https://www.lightningdesignsystem.com/components/combobox/#%22Input%22-markup) for select-only comboboxes.
-
-#### Custom Events
-
-**`change`**
-
-The event fired when an item is changed in the `lightning-input-address` component.
-
-The `change` event returns the following parameters.
-
-| Parameter  | Type   | Description                        |
-| ---------- | ------ | ---------------------------------- |
-| street     | string | The number and name of street.     |
-| city       | string | The name of the city.              |
-| province   | string | The name of the province/state.    |
-| country    | string | The name of the country.           |
-| postalCode | string | The postal code for the address.   |
-| validity   | object | The validity state of the element. |
-
-The `change` event properties are as follows.
-
-| Property   | Value | Description                                                                                               |
-| ---------- | ----- | --------------------------------------------------------------------------------------------------------- |
-| bubbles    | true  | This event bubbles up through the DOM.                                                                    |
-| cancelable | false | This event has no default behavior that can be canceled. You can't call `preventDefault()` on this event. |
-| composed   | true  | This event propagates outside of the component in which it was dispatched.                                |

package/src/lightning/inputAddress/__examples__/base/base.html

@@ -1,17 +0,0 @@
-<template>
-    <lightning-input-address
-        address-label="Address"
-        street-label="Street"
-        city-label="City"
-        country-label="Country"
-        province-label="Province"
-        postal-code-label="PostalCode"
-        street="121 Spear St."
-        city="San Francisco"
-        country="US"
-        province="CA"
-        postal-code="94105"
-        required
-        field-level-help="Help Text for inputAddress field" ></lightning-input-address>
-</template>
-    

package/src/lightning/inputAddress/__examples__/customLocale/customLocale.html

@@ -1,12 +0,0 @@
-<template>
-    <lightning-input-address
-        address-label="Address"
-        street-label="Street"
-        city-label="City"
-        country-label="Country"
-        province-label="Prefecture"
-        postal-code-label="Postal Code"
-        locale="ja-JP"
-        field-level-help="Help Text for input address field" >
-    </lightning-input-address>
-</template>

package/src/lightning/inputAddress/__examples__/stateAndCountryPicklists/stateAndCountryPicklists.html

@@ -1,18 +0,0 @@
-<template>
-    <lightning-input-address
-        address-label="Address"
-        street-label="Street"
-        city-label="City"
-        country-label="Country"
-        province-label="Province"
-        postal-code-label="PostalCode"
-        street={address.street}
-        city={address.city}
-        country={address.country}
-        province={address.province}
-        postal-code={address.postalCode}
-        field-level-help="Help Text for inputAddress field" 
-        country-options={getCountryOptions}
-        province-options={getProvinceOptions}
-        onchange={handleChange} ></lightning-input-address>
-</template>

package/src/lightning/inputAddress/inputAddress.js-meta.xml

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<LightningComponentBundle xmlns="xmlns=http://soap.sforce.com/2006/04/metadata">
-    <minApiVersion>42.0</minApiVersion>
-    <isExposed>true</isExposed>
-    <support>GA</support>
-    <capabilities>
-        <capability>lightning__ServerRenderableWithHydration</capability>
-    </capabilities>
-</LightningComponentBundle>