-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DATAP-1392 - update dependencies, update markup for text inputs and search inputs #514
Conversation
34752d4
to
9cfed16
Compare
I added a less loader path option so the cf-forms error doesn't appear anymore, but the buttons inside of the inputs appear broken. @anselmbradford if you get a chance, could you take a look at these? |
@flacoman91 Hmm I suspect cfpb/design-system#1979 |
1a9da9b
to
73ac7bb
Compare
73ac7bb
to
b264d9f
Compare
If it makes it easier, the date inputs technically don't need a clear since they have it in the default calendar UI. See https://cfpb.github.io/design-system/components/date-picker |
We'll need to rethink that. |
Gotcha! That's great feedback. Yeah use what you need and I'll bring this example up when we revisit the date input in the DS. |
fixing search bar text area fixing z-index of spyglass icon getting typeahead to work correctly with styling. move button around, fix date filter async typeahead text fix update some stuff update filter and snapshot hide cancel button if no value update more deps, fixing cypress tests fix warnings and nags fix error styles, remove clear button, fixing styles in mobile view.
514a54d
to
3099ac7
Compare
@anselmbradford i figured it out. We can set the min/max values if the value is empty in the onChange handler. |
Sorry for the rapid fire commits. This is ready now. |
{errors.length | ||
? errors.map((message, key) => ( | ||
{errors.length ? ( | ||
<div className="a-form-alert a-form-alert__error" role="alert"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update a-form-alert__error
to a-form-alert--error
{errors.length | ||
? errors.map((message, key) => ( | ||
{errors.length ? ( | ||
<div className="a-form-alert a-form-alert__error" role="alert"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<div className="a-form-alert a-form-alert__error" role="alert"> | |
<div className="a-form-alert a-form-alert--error" role="alert"> |
<svg | ||
className="cf-icon-svg cf-icon-delete-round" | ||
<div | ||
className="a-form-alert a-form-alert__error" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
className="a-form-alert a-form-alert__error" | |
className="a-form-alert a-form-alert--error" |
disabled={isDisabled} | ||
inputProps={{ | ||
id: htmlId, | ||
className: 'a-text-input a-text-input__full', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
className: 'a-text-input a-text-input__full', | |
className: 'a-text-input a-text-input--full', |
onChange={handleChange} | ||
onKeyDown={handlePressEnter} | ||
className={'a-text-input a-text-input__full ' + className} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
className={'a-text-input a-text-input__full ' + className} | |
className={'a-text-input a-text-input--full ' + className} |
@@ -100,6 +89,13 @@ | |||
background-color: var(--gray-10); | |||
} | |||
} | |||
|
|||
.o-search-input__input { | |||
//display: block; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be deleted?
.o-search-input__input { | ||
//display: block; | ||
&-label { | ||
z-index: 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why's this necessary? Maybe add a code comment. Is it possible to put the z-index on the parent o-search-input
, so that you're not customizing the component internals?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
)} | ||
inputProps={{ | ||
id: htmlId, | ||
className: 'a-text-input a-text-input__full', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
className: 'a-text-input a-text-input__full', | |
className: 'a-text-input a-text-input--full', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple modifiers that need updating from old BEM to new BEM, but otherwise GTG.
Whoops, looks like this may have auto gone in without the BEM updates |
I'll take care of it |
Addresses: DATAP-1392
Addresses: DATAP-1429
This PR: