-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: add typecheck to our documentation (#4267)
* typescript docs * save * add tsconfig check * refa card in iconlist * add to root command * test * update * test * test * test * undo * move in one file * test test test * test * update * maybe build * add build step for typecheck
- Loading branch information
Showing
24 changed files
with
519 additions
and
68 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
import { Slider } from '@marigold/components'; | ||
|
||
export default () => ( | ||
<Slider width="180px" aria-label="width"> | ||
<Slider width="full" aria-label="width"> | ||
Example | ||
</Slider> | ||
); |
12 changes: 1 addition & 11 deletions
12
docs/content/components/overlay/menu/menu-open-dialog.demo.tsx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,6 @@ import { | |
Form, | ||
Image, | ||
Inline, | ||
Menu, | ||
Select, | ||
Stack, | ||
Text, | ||
|
7 changes: 1 addition & 6 deletions
7
docs/content/foundations/form-fields/form-fields-required-state.demo.tsx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,108 @@ | ||
--- | ||
title: '@marigold/components' | ||
caption: 'Have a look on the latest changes regarding @marigold/components' | ||
badge: new | ||
toc: false | ||
--- | ||
|
||
## 10.0.0 (Released on <DateFormat value={new Date("Fri Oct 25 2024 18:15:28 GMT+0200 (Central European Summer Time)")} dateStyle="medium" />) | ||
|
||
### Major Changes | ||
|
||
- 65608b4: fix([DSTSUP-94]): Adjust date unavailable property from `<DatePicker>` | ||
|
||
**Breaking Change:** Adjusted `isDateUnavailable` prop to our code guidelines `dateUnavailable` | ||
|
||
Added disabled styles for `data-unavailable` in both b2b and core theme | ||
|
||
- caefbe4: refa(listbox): Allow sections in `<Combobox>` and `<Autocomplete>`, adjust Section API in `<Select>`, `<Combobox>` and `<Autocomplete>`. | ||
|
||
- Added the possibility to use sections with `<Combobox>` and `<Autocomplete>` | ||
- Refactored the `<Section>` (from `<Listbox>`) to fit our API, no need for the extra `<Header>` anymore. Instead you can do `<Select.Section header="My header">`, same for the other components | ||
- Renamed `<Item>` to `<Option>` in `<Combobox>` and `<Autocomplete>` to align with `<Select>` | ||
- Updated the docs for `<Select>`, `<Combobox>` and `<Autocomplete>` | ||
- Updated Storybook for `<Select>`, `<Combobox>` and `<Autocomplete>` with section stories | ||
- Renamed the part of the `<ListBox>` accordingly (from `sectionTitle` to `header`) | ||
|
||
**BREAKING CHANGE:** We changed the API of the `<Section>` component that is used in `<Select>`, `<Combobox>` and `<Autocomplete>`. It is no longer necessary to add a `Header` within the `<Section>`. | ||
|
||
Use the newly added `header` prop instead. Additionally, to unify the APIs all choices of `<Select>`, `<Combobox>` and `<Autocomplete>` are now called `<Option>` instead of `<Item>`. | ||
|
||
- 2d9917f: **Breaking changes** | ||
|
||
- `Dialog.Headline` has been renamed to `Dialog.Title`. Please update your code accordingly. | ||
- `<Dialog.Content>` and `<Dialog.Actions>` have been introduced for better organization and flexibility. | ||
- The internal layout now uses grid areas, ensuring consistent ordering and layout of the dialog elements. | ||
- Existing implementations of the `<Dialog>` component will need to be updated to use these new subcomponents. | ||
|
||
### Minor Changes | ||
|
||
- 6f8e3a2: style(dialog): make `<Dialog>` sizes responsive | ||
|
||
Using `size` with a `<Dialog>` will allow the dialog to be at most sm/md/lg wide. Will use full width on smaller screens. | ||
|
||
- 6687af7: refa: remove footer from `<Dialog>` + allow styles | ||
|
||
- dialogs can only have action now | ||
- align buttons in `<Dialog.Actions>` correctly | ||
|
||
- 2babc0b: feat(components): Mark layout components as regions for accessibility. | ||
|
||
Added the ability to mark layout components as regions (ARIA role). This improves accessibility by allowing assistive technologies to identify significant sections of the page, making navigation easier for users with disabilities. | ||
|
||
- 956982a: feat(components): Make `<Text>` and `<Headline>` accessible by allowing ARIA labelling props | ||
|
||
`<Text>` and `<Headline>` will no longer cause type errors when ARIA labelling is used (`aria-label`, `id`, ...). | ||
|
||
- df04623: Adding size to dialog component | ||
|
||
### Patch Changes | ||
|
||
- 7ea3838: feat(Menu): pass `aria-label` to menu button instead of menu | ||
- f18c8aa: [DST-494]: add loading states pattern | ||
|
||
[DST-494]: added prop `mode`to the `<XLoader />` to support inline and full-section loading | ||
|
||
- d5386e4: fix(components): Display `<Checkbox>` focus ring and adjust focus ring of `<Table>` | ||
|
||
Focus ring was not showing for the `<Checkbox>`. It does now! | ||
|
||
- 5c029ec: feat(components): Expose `Selection` type for easy usage with `Table` and other components | ||
|
||
When working with a `<Table>` you can now use | ||
|
||
```ts | ||
import type { Selection } from '@marigold/components'; | ||
``` | ||
|
||
instead of creating the type. | ||
|
||
- 2169b6f: bugfix([DSTSUP-92]): fixed variants in table stories | ||
|
||
At certain stories the control variants doesn't worked properly. Now it should work at least for all table stories. | ||
|
||
- bfd2843: chore: refa `<Text>` component. Based on the slot property it now takes the RAC text or not. Needed to prevent other components breaking. | ||
- 0e77996: docs([DST-572]): Adding a general form guideline in docs explaining different concepts such as when to use lable and help text | ||
- b8cd92a: feat: `CheckboxGroup` can now be used as a compound component | ||
|
||
- Refactored the `CheckboxGroup` to be a compound component and align it with other components: `<CheckboxGroup>` -> `<Checkbox.Group>` | ||
- Adjusted the Checkbox appearance demo a bit | ||
|
||
- 45fb3c4: chore(deps): update react-aria to 1.4 | ||
- f6a132c: docs([DST-582]): revise `<SectionMessage>` page according to new component page structure | ||
feat(components): add close button on `<SectionMessage>` | ||
|
||
Revised the `<SectionMessage>` documentation page to our new layout of component pages. And added a close button to allow the user to dismiss the `<SectionMessage>` this is now aligned with our feedback message pattern. | ||
|
||
- Updated dependencies [caefbe4] | ||
- Updated dependencies [6687af7] | ||
- Updated dependencies [2babc0b] | ||
- Updated dependencies [45fb3c4] | ||
- Updated dependencies [956982a] | ||
- @marigold/[email protected] | ||
- @marigold/[email protected] | ||
- @marigold/[email protected] | ||
|
||
## 9.0.2 (Released on <DateFormat value={new Date("Wed Sep 11 2024 14:52:49 GMT+0200 (Central European Summer Time)")} dateStyle="medium" />) | ||
|
||
### Patch Changes | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.