-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
prototype(chips): MDC chip APIs match existing APIs #16145
Conversation
14f0237
to
bf5e72f
Compare
Hey! I pushed the new MDC chip classes with the structure we discussed. I'm looking to get feedback on this partial implementation, and ideally get it submitted on its own. Known big missing things:
Open questions:
Next steps:
|
bce13bd
to
e80c090
Compare
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.
Overall looks good to me. This made me realize we have some stale patterns in the chip-list that we should clean up eventually (like overuse of any
in the value space), but that's a job for another time.
/** Default options, for the chips module, that can be overridden. */ | ||
export interface MatChipsDefaultOptions { | ||
/** The list of key codes that will trigger a chipEnd event. */ | ||
separatorKeyCodes: number[] | Set<number>; |
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.
FYI we decided just two days ago that we're going to change the way we handle these separator keys in the chips. It turns out that virtual keyboards on iOS and Android don't actually send keyCodes (or Keyboardevent.key
), so we're going to deprecate this API and and change to something like delimiterCharacters
and instead base the behavior off of the value in the input, with special casing for tab and enter. No action required for right now, but worth keeping in mind when you get to the board handling. I'll be sure to keep you in the loop when we figure out the final behavior we want.
notifyTrailingIconInteraction: () => this.trailingIconInteraction.emit(this.id), | ||
notifyRemoval: () => this.removed.emit({chip: this}), | ||
getComputedStyleValue: (propertyName) => { | ||
return window.getComputedStyle(this._mdcChip.nativeElement).getPropertyValue(propertyName); |
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.
@mmalerba will this cause a problem with SSR?
7d6145d
to
687d6a7
Compare
This comment has been minimized.
This comment has been minimized.
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.
Last a few last things I noticed on another pass
For the build issue:
|
4ddcc2f
to
4aa4c84
Compare
I updated the version of material-components-web in package.json, and 'yarn test' started passing locally. When I pushed to Github, I got yarn.lock out of date errors. I ran 'yarn install' to update it, and pushed again. Now everything on circle cl is failing at the restore cache step with permission denied errors. Is this expected? |
Looks like the CI might just be a transient error? I'd try rebasing and pushing again cc @devversion |
@jelbourn I think that I caused this issue while working on the Angular update where I might have stored a new cache entry in CircleCI (with a new docker image user). Rebasing should ensure that a more recent cache entry is used (which should not be polluted by my Angular update PR) |
I rebased and pushed again, but I'm still getting the same permission denied errors.
cc @devversion |
@devversion any further ideas? I tried this on another PR (#16335) and the same thing happens. I don't see anything in the CircleCI UI to manually clear the cache like existed in Travis. Could it have anything to do with the |
@vanessanschmitt The issues have been sorted out. Can you please try to rebase? Thank you! |
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.
LGTM
related to #16173 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Work in progress, just looking for feedback! Will keep updating as I work.