Skip to content
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

PI-1066 fixed bug with minify card #116

Merged
merged 1 commit into from
Apr 6, 2017
Merged

Conversation

thellimist
Copy link
Contributor

item does not have value attribute. It's just a string.

We've update cf-component-checkbox to 3.0.1 a month ago. But I've checked whether it was a bug caused by us or cf-ui. It seems like cf-ui update did not cause the bug. More interestingly this part of code has not been changed for 11 months. I remember testing every future before WP launch. So I've no idea how we introduced this bug. Also no one actually noticed it for a year...

Currently cf-ui is doing lots of updates. I'm happy with the current version so I choose not to update cf-component-checkbox to 3.2.0 which is the newest version.

@jwineman
Copy link
Contributor

jwineman commented Apr 6, 2017

Yeah I want to avoid updating cf-ui components until the fela migration is complete.

@jwineman
Copy link
Contributor

jwineman commented Apr 6, 2017

I bet this bug was introduced at the same time the <Select/> but was. We changed form components from passing the value to passing the entire event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants