This commit adds the exports entry in each package.json, exposing the public parts of each package and hiding the private ones. |
||
|---|---|---|
| .. | ||
| docs/helpers | ||
| src | ||
| test | ||
| CHANGELOG.md | ||
| index.js | ||
| lion-fieldset.js | ||
| package.json | ||
| README.md | ||
Fieldset
lion-fieldset groups multiple input fields or other fieldsets together.
import { html } from '@lion/core';
import '@lion/input/lion-input.js';
import { localize } from '@lion/localize';
import { MinLength, Validator, Required } from '@lion/form-core';
import './lion-fieldset.js';
import './docs/helpers/demo-fieldset-child.js';
export default {
title: 'Forms/Fieldset/Overview',
};
We have three specific fieldset implementations:
export const main = () => html`
<lion-fieldset name="nameGroup" label="Name">
<lion-input name="FirstName" label="First Name"></lion-input>
<lion-input name="LastName" label="Last Name"></lion-input>
</lion-fieldset>
`;
A native fieldset element should always have a legend-element for a11y purposes.
However, our fieldset element is not native and should not have a legend-element.
Our fieldset instead has a label attribute or you can add a label with a div- or heading-element using slot="label".
Features
- Easy retrieval of form data based on field names
- Advanced user interaction scenarios via interaction states
- Can have validate on fieldset level and shows the validation feedback below the fieldset
- Can disable input fields on fieldset level
- Accessible out of the box
How to use
Installation
npm i --save @lion/fieldset
import { LionFieldset } from '@lion/fieldset';
// or
import '@lion/fieldset/lion-fieldset.js';
Example
<lion-fieldset name="personalia" label="personalia">
<lion-input name="title" label="Title"></lion-input>
</lion-fieldset>
For more examples please look at Fieldset Examples.