LeafyGreen UI – LeafyGreen's React UI Kit
APACHE-2.0 License
Bot releases are visible (Hide)
Published by github-actions[bot] 6 months ago
c406ab85: LG-4135
'small'
and 'large'
size variants'xsmall'
varianterrorMessage
and successMessage
propserrorMessage
will render a default of 'This input needs your attention'
and can be customizederrorMessage
will only render when state
is warning
or error
successMessage
will render a default of 'Success'
and can be customizedsuccessMessage
will only render when state
is valid
aria-describedby
is undefined and stateNotifications
is not an arrayPublished by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
c406ab85: LG-4134
'small'
and 'xsmall'
size variants'large'
variantAdded default errorMessage
of 'This input needs your attention'
Added valid
state variant and successMessage
prop
successMessage
will render a default of 'Success'
and can be customizedsuccessMessage
will only render when state=valid
Published by github-actions[bot] 6 months ago
c406ab85: LG-2930
FormFieldFeedback
componentDEFAULT_MESSAGES
constantFormField
and FormFieldInputContainer
components to use tokens where possibleFormField
to use FormFieldFeedback
Published by github-actions[bot] 6 months ago
c406ab85: LG-2930
DatePicker
test specsUpdated dependencies [c406ab85]
Updated dependencies [c406ab85]
Updated dependencies [c406ab85]
Updated dependencies [c406ab85]
Published by github-actions[bot] 6 months ago
c406ab85: LG-4133
'small'
, 'xsmall'
, and 'large'
size variantsA default errorMessage
of 'This input needs your attention'
will render below combobox when state is invalid.
Added a valid
state with success icon and successMessage
prop. A default successMessage
of 'Success'
will render when state is valid. successMessage
prop allows customization.
Disabled Combobox
component no longer renders the disabled
attribute and instead relies on aria-disabled
and readonly
attributes.
The last change is made to ensure that disabled components are still focusable to users using keyboard navigation.
For more on aria-disabled
see the documentation on MDN
Functionally, migration should be seamless, however there may be unit/integration/e2e tests that relied on this behavior.
Generally, only this repo should need to test that these components have a specific attribute. We recommend updating unit tests to check that some event was or was not called.
However, there are cases where this may still need to be tested. You can replace any expect(combobox).toBeDisabled()
with an explicit check for expect(combobox).toHaveAttribute('aria-disabled', 'true')
.
Similar to unit tests, you should generally test functionality and not implementation details. However, to test this in Cypress replace any cy.get(combobox).should('be.disabled');
checks with cy.get(combobox).invoke('attr', 'aria-disabled').should('eq', 'true');
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
rollup
and related packages to v4Published by github-actions[bot] 6 months ago
satisfies
to ensure consistent & correct colors
token structurePublished by github-actions[bot] 6 months ago
MenuGroup
from packagePublished by github-actions[bot] 6 months ago
data-lgid
to storybookExcludedControlParams
and storybookExcludedArgTypes
.Published by github-actions[bot] 6 months ago
Link
component so that:
display: inline-flex
Typography
componentPublished by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
cbfda91b: LG-4144
FormField
styling changes apply to TextArea
. See style changes here
A default errorMessage
of 'This input needs your attention'
will render below text area when state is invalid.
A default successMessage
of 'Success'
will render when state is valid. successMessage
prop accepts a custom string.
Disabled TextArea
component no longer renders the disabled
attribute and instead relies on aria-disabled
and readonly
attributes.
The last change is made to ensure that disabled components are still focusable to users using keyboard navigation.
For more on aria-disabled
see the documentation on MDN
Functionally, migration should be seamless, however there may be unit/integration/e2e tests that relied on this behavior.
Generally, only this repo should need to test that these components have a specific attribute. We recommend updating unit tests to check that some event was or was not called.
However, there are cases where this may still need to be tested. In cases where a test checks expect(textArea).toBeDisabled()
, you can replace and use test harnesses.
Similar to unit tests, you should generally test functionality and not implementation details. However, to test this in Cypress replace any cy.get(textArea).should('be.disabled');
checks with cy.get(textArea).invoke('attr', 'aria-disabled').should('eq', 'true');
Published by github-actions[bot] 6 months ago