Skip to content

multiselect: put back custom-label & fix #87

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

Closed
icebob opened this issue Oct 6, 2016 · 2 comments
Closed

multiselect: put back custom-label & fix #87

icebob opened this issue Oct 6, 2016 · 2 comments

Comments

@icebob
Copy link
Member

icebob commented Oct 6, 2016

I removed custom-label property from multiselect because give errors.
If it props doesn't exist in schema, multiselect try to call and gives error.

@icebob icebob added this to the v0.6.0 milestone Oct 6, 2016
@lionel-bijaoui
Copy link
Member

I had the same problem while working the v2, and found a solution. It need to at least (even when empty) return a function. I was returning null and it was not happy.
I will update my master and do a PR with the fix.

@icebob
Copy link
Member Author

icebob commented Oct 7, 2016

Merged. Thanks!

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

No branches or pull requests

2 participants