Releases: CMSgov/design-system
Releases · CMSgov/design-system
1.12.0
💅 Changes
- Added
aria-pressed to Select All and Clear All buttons in <MonthPicker> for screen reader context #235
- Change
$color-muted to reference $color-gray, rather than $color-gray-medium. This means the muted color becomes darker and can now be combined with a background that is $color-gray-lightest while still being accessible.
1.11.0
🚀 Added
- New
ds-u-border--dark utility class to set the border to a dark gray.
- New
$border-color-dark Sass variable
💅 Changes
- The markup of the
MonthPicker component has been updated to improve accessibility. As part of those changes, a new headingLevel prop has been added to the component.
🛠 Fixed
Array.find polyfill added to the Autocomplete component to fix IE11- Locked
uswds dependency version at 1.3.x. 1.4 renamed some variables that we depend on, which is a breaking change to our implementation.
1.10.0
💅 Changes
variation prop on <Button> now accepts all strings
🛠 Fixed
- Use Open Sans on
ds-c-field inputs, rather than the system font 🙈
.ds-c-step__actions has had a margin-left: auto added to fix alignment on IE11- Removed the need for adding punctuation to
<FormLabel>'s requirementLabel prop. This avoids adopters accidentally having a field description that says stuff like "Optional Enter the ID from your card", and should be more future-proof if we ever to decide to place the requirement label elsewhere.
📦 Internal
- Now when you run
yarn start:theme or yarn build:theme, the docs/ directory is placed into the theme's directory. This is useful for generating documentation for a theme and we'll use this for the HealthCare.gov site package's docs.
1.9.0
🚀 Added
- Added
onComponentBlur prop to <DateField>
- also added
dayInvalid, monthInvalid, yearInvalid boolean props added to DateField to support error styling on the individual input elements
💅 Changes
<Autocomplete>'s items prop is now optional- Updated the
DateField hint to include slashes, based on feedback from the CMS content team. It's now For example: 4/25/1986
- Changed weight of
requirementLabel in FormLabel from bold to normal
🛠 Fixed
- Fixed invalid HTML in
MonthPicker list #218
- Some props that were passed through to a child component were stricter than the original PropType. These were loosened in most cases from
string to node.
- Added
number as a valid PropType to TextField's defaultValue and value.
1.8.0
💅 Changes
- The
<Autocomplete> component now passes any undocumented props directly to Downshift, which is used internally for controlling the autocomplete interactions and state.
- Event handlers passed into the
TextField child of Autocomplete are now used cloned so that they're not overwritten.
onInputValueChange prop was added as a documented prop to Autocomplete for gathering child input value
1.7.0
🚀 Added
- Added a
<Dialog> React component to compliment the CSS/HTML Modal dialog component. #202
- Added a
<Autocomplete> React component. #201
💅 Changes
- Removed the
border from the primary button (ds-c-button--primary) so that it's background color can be controlled solely by the $button-primary-* variables. #209
- The
TextField component now accepts an id prop
1.6.1
🛠 Fixed
- Replaces relative image link with customizable
$image-path variable for the Dialog's close icon.
1.6.0
🚀 Added
-
Added <MonthPicker> component #196
-
Added <StepList> component #197
-
Added Dialog CSS component (.ds-c-dialog) and example HTML #198. A React component for this is coming soon
📦 Internal
- Fixed Yeoman generator issue caused by Prettier #194
- Refactored documentation generation to render React components separately in iframes #200 #203. Now supports Node 7 as well
1.5.0
💅 Changes
- Undocumented props passed to
<TextField> will now be added to the rendered input DOM node. This is the same behavior as <Choice>, <Select>, and <Button>. #192 - thanks @apobbati!
