lightning-base-components 1.27.5-alpha → 1.28.3-alpha

package/src/lightning/purifyLib/LICENSE.txt

@@ -1,378 +0,0 @@
-DOMPurify
-Copyright 2015 Mario Heiderich
-
-DOMPurify is free software; you can redistribute it and/or modify it under the
-terms of either:
-
-a) the Apache License Version 2.0, or
-b) the Mozilla Public License Version 2.0
-
------------------------------------------------------------------------------
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing, software
-    distributed under the License is distributed on an "AS IS" BASIS,
-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-    See the License for the specific language governing permissions and
-    limitations under the License.
-
------------------------------------------------------------------------------
-Mozilla Public License, version 2.0
-
-1. Definitions
-
-1.1. “Contributor”
-
-     means each individual or legal entity that creates, contributes to the
-     creation of, or owns Covered Software.
-
-1.2. “Contributor Version”
-
-     means the combination of the Contributions of others (if any) used by a
-     Contributor and that particular Contributor’s Contribution.
-
-1.3. “Contribution”
-
-     means Covered Software of a particular Contributor.
-
-1.4. “Covered Software”
-
-     means Source Code Form to which the initial Contributor has attached the
-     notice in Exhibit A, the Executable Form of such Source Code Form, and
-     Modifications of such Source Code Form, in each case including portions
-     thereof.
-
-1.5. “Incompatible With Secondary Licenses”
-     means
-
-     a. that the initial Contributor has attached the notice described in
-        Exhibit B to the Covered Software; or
-
-     b. that the Covered Software was made available under the terms of version
-        1.1 or earlier of the License, but not also under the terms of a
-        Secondary License.
-
-1.6. “Executable Form”
-
-     means any form of the work other than Source Code Form.
-
-1.7. “Larger Work”
-
-     means a work that combines Covered Software with other material, in a separate
-     file or files, that is not Covered Software.
-
-1.8. “License”
-
-     means this document.
-
-1.9. “Licensable”
-
-     means having the right to grant, to the maximum extent possible, whether at the
-     time of the initial grant or subsequently, any and all of the rights conveyed by
-     this License.
-
-1.10. “Modifications”
-
-     means any of the following:
-
-     a. any file in Source Code Form that results from an addition to, deletion
-        from, or modification of the contents of Covered Software; or
-
-     b. any new file in Source Code Form that contains any Covered Software.
-
-1.11. “Patent Claims” of a Contributor
-
-      means any patent claim(s), including without limitation, method, process,
-      and apparatus claims, in any patent Licensable by such Contributor that
-      would be infringed, but for the grant of the License, by the making,
-      using, selling, offering for sale, having made, import, or transfer of
-      either its Contributions or its Contributor Version.
-
-1.12. “Secondary License”
-
-      means either the GNU General Public License, Version 2.0, the GNU Lesser
-      General Public License, Version 2.1, the GNU Affero General Public
-      License, Version 3.0, or any later versions of those licenses.
-
-1.13. “Source Code Form”
-
-      means the form of the work preferred for making modifications.
-
-1.14. “You” (or “Your”)
-
-      means an individual or a legal entity exercising rights under this
-      License. For legal entities, “You” includes any entity that controls, is
-      controlled by, or is under common control with You. For purposes of this
-      definition, “control” means (a) the power, direct or indirect, to cause
-      the direction or management of such entity, whether by contract or
-      otherwise, or (b) ownership of more than fifty percent (50%) of the
-      outstanding shares or beneficial ownership of such entity.
-
-
-2. License Grants and Conditions
-
-2.1. Grants
-
-     Each Contributor hereby grants You a world-wide, royalty-free,
-     non-exclusive license:
-
-     a. under intellectual property rights (other than patent or trademark)
-        Licensable by such Contributor to use, reproduce, make available,
-        modify, display, perform, distribute, and otherwise exploit its
-        Contributions, either on an unmodified basis, with Modifications, or as
-        part of a Larger Work; and
-
-     b. under Patent Claims of such Contributor to make, use, sell, offer for
-        sale, have made, import, and otherwise transfer either its Contributions
-        or its Contributor Version.
-
-2.2. Effective Date
-
-     The licenses granted in Section 2.1 with respect to any Contribution become
-     effective for each Contribution on the date the Contributor first distributes
-     such Contribution.
-
-2.3. Limitations on Grant Scope
-
-     The licenses granted in this Section 2 are the only rights granted under this
-     License. No additional rights or licenses will be implied from the distribution
-     or licensing of Covered Software under this License. Notwithstanding Section
-     2.1(b) above, no patent license is granted by a Contributor:
-
-     a. for any code that a Contributor has removed from Covered Software; or
-
-     b. for infringements caused by: (i) Your and any other third party’s
-        modifications of Covered Software, or (ii) the combination of its
-        Contributions with other software (except as part of its Contributor
-        Version); or
-
-     c. under Patent Claims infringed by Covered Software in the absence of its
-        Contributions.
-
-     This License does not grant any rights in the trademarks, service marks, or
-     logos of any Contributor (except as may be necessary to comply with the
-     notice requirements in Section 3.4).
-
-2.4. Subsequent Licenses
-
-     No Contributor makes additional grants as a result of Your choice to
-     distribute the Covered Software under a subsequent version of this License
-     (see Section 10.2) or under the terms of a Secondary License (if permitted
-     under the terms of Section 3.3).
-
-2.5. Representation
-
-     Each Contributor represents that the Contributor believes its Contributions
-     are its original creation(s) or it has sufficient rights to grant the
-     rights to its Contributions conveyed by this License.
-
-2.6. Fair Use
-
-     This License is not intended to limit any rights You have under applicable
-     copyright doctrines of fair use, fair dealing, or other equivalents.
-
-2.7. Conditions
-
-     Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in
-     Section 2.1.
-
-
-3. Responsibilities
-
-3.1. Distribution of Source Form
-
-     All distribution of Covered Software in Source Code Form, including any
-     Modifications that You create or to which You contribute, must be under the
-     terms of this License. You must inform recipients that the Source Code Form
-     of the Covered Software is governed by the terms of this License, and how
-     they can obtain a copy of this License. You may not attempt to alter or
-     restrict the recipients’ rights in the Source Code Form.
-
-3.2. Distribution of Executable Form
-
-     If You distribute Covered Software in Executable Form then:
-
-     a. such Covered Software must also be made available in Source Code Form,
-        as described in Section 3.1, and You must inform recipients of the
-        Executable Form how they can obtain a copy of such Source Code Form by
-        reasonable means in a timely manner, at a charge no more than the cost
-        of distribution to the recipient; and
-
-     b. You may distribute such Executable Form under the terms of this License,
-        or sublicense it under different terms, provided that the license for
-        the Executable Form does not attempt to limit or alter the recipients’
-        rights in the Source Code Form under this License.
-
-3.3. Distribution of a Larger Work
-
-     You may create and distribute a Larger Work under terms of Your choice,
-     provided that You also comply with the requirements of this License for the
-     Covered Software. If the Larger Work is a combination of Covered Software
-     with a work governed by one or more Secondary Licenses, and the Covered
-     Software is not Incompatible With Secondary Licenses, this License permits
-     You to additionally distribute such Covered Software under the terms of
-     such Secondary License(s), so that the recipient of the Larger Work may, at
-     their option, further distribute the Covered Software under the terms of
-     either this License or such Secondary License(s).
-
-3.4. Notices
-
-     You may not remove or alter the substance of any license notices (including
-     copyright notices, patent notices, disclaimers of warranty, or limitations
-     of liability) contained within the Source Code Form of the Covered
-     Software, except that You may alter any license notices to the extent
-     required to remedy known factual inaccuracies.
-
-3.5. Application of Additional Terms
-
-     You may choose to offer, and to charge a fee for, warranty, support,
-     indemnity or liability obligations to one or more recipients of Covered
-     Software. However, You may do so only on Your own behalf, and not on behalf
-     of any Contributor. You must make it absolutely clear that any such
-     warranty, support, indemnity, or liability obligation is offered by You
-     alone, and You hereby agree to indemnify every Contributor for any
-     liability incurred by such Contributor as a result of warranty, support,
-     indemnity or liability terms You offer. You may include additional
-     disclaimers of warranty and limitations of liability specific to any
-     jurisdiction.
-
-4. Inability to Comply Due to Statute or Regulation
-
-   If it is impossible for You to comply with any of the terms of this License
-   with respect to some or all of the Covered Software due to statute, judicial
-   order, or regulation then You must: (a) comply with the terms of this License
-   to the maximum extent possible; and (b) describe the limitations and the code
-   they affect. Such description must be placed in a text file included with all
-   distributions of the Covered Software under this License. Except to the
-   extent prohibited by statute or regulation, such description must be
-   sufficiently detailed for a recipient of ordinary skill to be able to
-   understand it.
-
-5. Termination
-
-5.1. The rights granted under this License will terminate automatically if You
-     fail to comply with any of its terms. However, if You become compliant,
-     then the rights granted under this License from a particular Contributor
-     are reinstated (a) provisionally, unless and until such Contributor
-     explicitly and finally terminates Your grants, and (b) on an ongoing basis,
-     if such Contributor fails to notify You of the non-compliance by some
-     reasonable means prior to 60 days after You have come back into compliance.
-     Moreover, Your grants from a particular Contributor are reinstated on an
-     ongoing basis if such Contributor notifies You of the non-compliance by
-     some reasonable means, this is the first time You have received notice of
-     non-compliance with this License from such Contributor, and You become
-     compliant prior to 30 days after Your receipt of the notice.
-
-5.2. If You initiate litigation against any entity by asserting a patent
-     infringement claim (excluding declaratory judgment actions, counter-claims,
-     and cross-claims) alleging that a Contributor Version directly or
-     indirectly infringes any patent, then the rights granted to You by any and
-     all Contributors for the Covered Software under Section 2.1 of this License
-     shall terminate.
-
-5.3. In the event of termination under Sections 5.1 or 5.2 above, all end user
-     license agreements (excluding distributors and resellers) which have been
-     validly granted by You or Your distributors under this License prior to
-     termination shall survive termination.
-
-6. Disclaimer of Warranty
-
-   Covered Software is provided under this License on an “as is” basis, without
-   warranty of any kind, either expressed, implied, or statutory, including,
-   without limitation, warranties that the Covered Software is free of defects,
-   merchantable, fit for a particular purpose or non-infringing. The entire
-   risk as to the quality and performance of the Covered Software is with You.
-   Should any Covered Software prove defective in any respect, You (not any
-   Contributor) assume the cost of any necessary servicing, repair, or
-   correction. This disclaimer of warranty constitutes an essential part of this
-   License. No use of  any Covered Software is authorized under this License
-   except under this disclaimer.
-
-7. Limitation of Liability
-
-   Under no circumstances and under no legal theory, whether tort (including
-   negligence), contract, or otherwise, shall any Contributor, or anyone who
-   distributes Covered Software as permitted above, be liable to You for any
-   direct, indirect, special, incidental, or consequential damages of any
-   character including, without limitation, damages for lost profits, loss of
-   goodwill, work stoppage, computer failure or malfunction, or any and all
-   other commercial damages or losses, even if such party shall have been
-   informed of the possibility of such damages. This limitation of liability
-   shall not apply to liability for death or personal injury resulting from such
-   party’s negligence to the extent applicable law prohibits such limitation.
-   Some jurisdictions do not allow the exclusion or limitation of incidental or
-   consequential damages, so this exclusion and limitation may not apply to You.
-
-8. Litigation
-
-   Any litigation relating to this License may be brought only in the courts of
-   a jurisdiction where the defendant maintains its principal place of business
-   and such litigation shall be governed by laws of that jurisdiction, without
-   reference to its conflict-of-law provisions. Nothing in this Section shall
-   prevent a party’s ability to bring cross-claims or counter-claims.
-
-9. Miscellaneous
-
-   This License represents the complete agreement concerning the subject matter
-   hereof. If any provision of this License is held to be unenforceable, such
-   provision shall be reformed only to the extent necessary to make it
-   enforceable. Any law or regulation which provides that the language of a
-   contract shall be construed against the drafter shall not be used to construe
-   this License against a Contributor.
-
-
-10. Versions of the License
-
-10.1. New Versions
-
-      Mozilla Foundation is the license steward. Except as provided in Section
-      10.3, no one other than the license steward has the right to modify or
-      publish new versions of this License. Each version will be given a
-      distinguishing version number.
-
-10.2. Effect of New Versions
-
-      You may distribute the Covered Software under the terms of the version of
-      the License under which You originally received the Covered Software, or
-      under the terms of any subsequent version published by the license
-      steward.
-
-10.3. Modified Versions
-
-      If you create software not governed by this License, and you want to
-      create a new license for such software, you may create and use a modified
-      version of this License if you rename the license and remove any
-      references to the name of the license steward (except to note that such
-      modified license differs from this License).
-
-10.4. Distributing Source Code Form that is Incompatible With Secondary Licenses
-      If You choose to distribute Source Code Form that is Incompatible With
-      Secondary Licenses under the terms of this version of the License, the
-      notice described in Exhibit B of this License must be attached.
-
-Exhibit A - Source Code Form License Notice
-
-      This Source Code Form is subject to the
-      terms of the Mozilla Public License, v.
-      2.0. If a copy of the MPL was not
-      distributed with this file, You can
-      obtain one at
-      http://mozilla.org/MPL/2.0/.
-
-If it is not possible or desirable to put the notice in a particular file, then
-You may include the notice in a location (such as a LICENSE file in a relevant
-directory) where a recipient would be likely to look for such a notice.
-
-You may add additional accurate notices of copyright ownership.
-
-Exhibit B - “Incompatible With Secondary Licenses” Notice
-
-      This Source Code Form is “Incompatible
-      With Secondary Licenses”, as defined by
-      the Mozilla Public License, v. 2.0.
-

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

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

package/src/lightning/purifyLib/purifyLib.ts

@@ -1,20 +0,0 @@
-import DOMPurify from './purify.js';
-
-interface SanitizeConfig {
-    // Define specific properties of the configuration object if known
-    [key: string]: any;
-}
-
-/**
- * Sanitize method providing core sanitation functionality
- *
- * @param {string | Node} dirty - string or DOM node
- * @param {SanitizeConfig} config - configuration object
- * @return {string} sanitized string
- */
-export default function sanitizeHTML(
-    dirty: string | Node,
-    config?: SanitizeConfig
-): string {
-    return DOMPurify.sanitize(dirty, config);
-}

package/src/lightning/radioGroup/__docs__/radioGroup.md

@@ -1,197 +0,0 @@
----
-examples:
-    - name: basic
-      label: Basic Radio Group
-      description: A radio group contains at least two options and only one can be selected.
-    - name: required
-      label: Required Radio Group
-      description: A radio group displays a field-level error if it's required and no option is selected after the first interaction.
-    - name: disabled
-      label: Disabled Radio Group
-      description: Disabled options are grayed out and you can't interact with them.
-    - name: button
-      label: Radio Group with Button Type
-      description: A radio group can use the button type to display a different visual style.
-    - name: buttonrequired
-      label: Required Radio Group with Button Type
-      description: A radio button group displays a field-level error if it's required and no option is selected after the first interaction.
-    - name: buttondisabled
-      label: Disabled Radio Group with Button Type
-      description: Disabled options are grayed out and you can't interact with them.
----
-
-A `lightning-radio-group` component represents a group of radio buttons that permit only
-one button to be selected at a time. The component renders radio button `<input>` elements
-and assigns the same value to the `name` attribute for each element. The common
-`name` attribute joins the elements in a group. If you select any radio button in that
-group, any previously selected button in the group is deselected.
-
-In general, we don't recommend setting the `name` attribute in `lightning-radio-group`.
-The component automatically generates a unique value for `name` if none is provided. The generated value ensures
-a common name for the `<input>` elements rendered for the radio button group, and is unique in the page.
-
-See **Reusing `lightning-radio-group` in a Page** for `name` attribute considerations if you want to use the component multiple times in a page.
-
-If the `required` attribute is specified, at least one radio button must be selected.
-When a user interacts with the radio button group and doesn't make a selection, an
-error message is displayed.
-
-If the `disabled` attribute is specified, radio button selections can't be changed.
-
-This example creates a radio button group with two options and `option1` is selected
-by default. One radio button must be selected as the `required` attribute is
-specified.
-
-```html
-<template>
-    <lightning-radio-group
-        label="Radio Button Group"
-        options={options}
-        value={value}
-        onchange={handleChange}
-        required
-    >
-    </lightning-radio-group>
-</template>
-```
-
-You can check which values are selected by using the `value` attribute.
-To retrieve the values when the selection is changed, use the `onchange` event handler and call
-`event.detail.value`.
-
-```javascript
-import { LightningElement } from 'lwc';
-export default class MyComponentName extends LightningElement {
-    options = [
-        { label: 'Ross', value: 'option1' },
-        { label: 'Rachel', value: 'option2' },
-    ];
-
-    // Select option1 by default
-    value = 'option1';
-
-    handleChange(event) {
-        const selectedOption = event.detail.value;
-        console.log('Option selected with value: ' + selectedOption);
-    }
-}
-```
-
-#### Creating Radio Buttons
-
-To create radio buttons, pass in the following properties to the `options` attribute.
-
-| Property | Type   | Description                                                        |
-| -------- | ------ | ------------------------------------------------------------------ |
-| label    | string | The text that displays next to a radio button.                     |
-| value    | string | The string that's used to identify which radio button is selected. |
-
-#### Input Validation
-
-A radio group that's disabled is always valid. If the radio group is marked required and no option is selected, after you remove focus from the radio group an error message is displayed.
-
-You can override the default message using `message-when-value-missing` when a radio group is required and no option is selected. This message is displayed when you remove focus from the radio group.
-
-```html
-<form onsubmit={handleSubmit}>
-    <lightning-radio-group name="radioGroup"
-        label="Will you be attending the event?"
-        options={options}
-        value={value}
-        type="radio"
-        lwc:ref="radiogroup"
-        message-when-value-missing="Select an option"
-        required></lightning-radio-group>
-    <lightning-button variant="brand" label="Submit" onclick={handleSubmit} type="submit"></lightning-button>
-</form>
-```
-
-To programmatically display error messages on invalid fields, use the `reportValidity()` method. This method returns false if the input is invalid.
-
-For custom error messages, display the message using `setCustomValidity()` and `reportValidity()`. For more information, see the [lightning-input](/docs/component-library/bundle/lightning-input/documentation) documentation.
-
-```javascript
-import { LightningElement } from 'lwc';
-export default class ValidationExample extends LightningElement {
-
-  value = '';
-  get options() {
-    return [
-      { label: 'Yes', value: 'yes' },
-      { label: 'No', value: 'no' },
-    ];
-  }
-
-  handleSubmit(e) {
-    const allValid = this.refs.radiogroup.reportValidity();
-    if (!allValid) {
-      e.preventDefault();
-      this.refs.radiogroup.setCustomValidity("Please select an option");
-      this.refs.radiogroup.showHelpMessageIfInvalid();
-    }
-  }
-```
-
-If you're creating a form for Salesforce record data, we recommend using [`lightning-record-form`](/docs/component-library/bundle/lightning-record-form), [`lightning-record-edit-form`](/docs/component-library/bundle/lightning-record-edit-form), or [`lightning-record-view-form`](/docs/component-library/bundle/lightning-record-view-form). The record form 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).
-
-#### Reusing `lightning-radio-group` in a Page
-
-To reuse `lightning-radio-group` in a page or across multiple tabs such as in a Salesforce console app,
-follow one of these suggestions.
-
-- Omit the `name` attribute to enable the component to automatically generate a unique name.
-- Enclose each `lightning-radio-group` component in a `<form>` element and provide your own value for `name`.
-
-If the reused component generates a unique name, each radio button group in the page renders
-`<input>` elements grouped correctly so that one value can be selected in each group.
-
-If you provide your own `name` value and reuse the
-component with the same name, each radio button group in the page uses the same `name` value for the `<input>` elements.
-The result is that you can select only one value across all radio button groups, instead of
-one value within a radio button group. If you require your own `name` value, enclose the
-reused components in `<form>` elements to enable the page to use the same `name` value for multiple radio
-button groups.
-
-#### Component Styling
-
-`lightning-radio-group` implements the
-[radio button](https://www.lightningdesignsystem.com/components/radio-group/) blueprint in the
-Salesforce Lightning Design System (SLDS).
-
-Set `type="button"` to create a component that implements the
-[radio button group](https://www.lightningdesignsystem.com/components/radio-button-group/) blueprint in SLDS.
-
-##### Variants
-
-Use the `variant` attribute with one of these values to change the appearance of the radio group.
-
-- `label-hidden` hides the radio group label but makes it available to assistive technology. This variant does not hide the option labels.
-- `label-inline` horizontally aligns the label and radio group.
-- `label-stacked` places the label above the radio group.
-- `standard` is the default variant, which displays the radio group label above the options.
-
-##### 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 a margin around the radio group using an SLDS class.
-
-```html
-<lightning-radio-group
-    label="Radio Group"
-    options={options}
-    value={value}
-    class="slds-m-around_x-small"
->
-</lightning-radio-group>
-```
-
-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 [Radio Group: Styling Hooks Overview](https://www.lightningdesignsystem.com/components/radio-group/#Styling-Hooks-Overview) for documentation on component-specific hooks for this component.
-
-#### Accessibility
-
-The radio group is nested in a `fieldset` element that contains a `legend`
-element. The legend contains the `label` value. The `fieldset` element enables
-grouping of related radio buttons to facilitate tabbing navigation and speech
-navigation for accessibility purposes. Similarly, the `legend` element
-improves accessibility by enabling a caption to be assigned to the `fieldset`.

package/src/lightning/radioGroup/__examples__/basic/basic.html

@@ -1,7 +0,0 @@
-<template>
-    <lightning-radio-group name="radioGroup"
-                          label="Radio Group"
-                          options={options}
-                          value={value}
-                          type="radio"></lightning-radio-group>
-</template>

package/src/lightning/radioGroup/__examples__/button/button.html

@@ -1,7 +0,0 @@
-<template>
-    <lightning-radio-group name="radioGroup"
-                          label="Radio Group"
-                          options={options}
-                          value={value}
-                          type="button"></lightning-radio-group>
-</template>

package/src/lightning/radioGroup/__examples__/buttondisabled/buttondisabled.html

@@ -1,8 +0,0 @@
-<template>
-    <lightning-radio-group name="radioGroup"
-                           label="Radio Group"
-                           options={options}
-                           value={value}
-                           disabled
-                           type="button"></lightning-radio-group>
-</template>

package/src/lightning/radioGroup/__examples__/buttonrequired/buttonrequired.html

@@ -1,8 +0,0 @@
-<template>
-    <lightning-radio-group name="radioGroup"
-                           label="Radio Group"
-                           options={options}
-                           value={value}
-                           required
-                           type="button"></lightning-radio-group>
-</template>

package/src/lightning/radioGroup/__examples__/disabled/disabled.html

@@ -1,8 +0,0 @@
-<template>
-    <lightning-radio-group name="radioGroup"
-                          label="Radio Group"
-                          options={options}
-                          value={value}
-                           disabled
-                          type="radio"></lightning-radio-group>
-</template>

package/src/lightning/radioGroup/__examples__/required/required.html

@@ -1,8 +0,0 @@
-<template>
-    <lightning-radio-group name="radioGroup"
-                          label="Radio Group"
-                          options={options}
-                          value={value}
-                           required
-                          type="radio"></lightning-radio-group>
-</template>

package/src/lightning/radioGroup/radioGroup.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>41.0</minApiVersion>
-    <support>GA</support>
-    <capabilities>
-        <capability>lightning__ServerRenderableWithHydration</capability>
-    </capabilities>
-</LightningComponentBundle>