This repository has been archived by the owner on Dec 23, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 208
Please export the defaultChipRenderer #206
Labels
Comments
@frenya It sounds like a great first PR anyway. 👍 |
frenya
added a commit
to frenya/material-ui-chip-input
that referenced
this issue
May 13, 2018
Exporting defaultChipRenderer allows better customisation in special cases. Addresses issue TeamWertarbyte#206.
If you insist ... 😄 |
leMaik
pushed a commit
that referenced
this issue
May 13, 2018
Exporting defaultChipRenderer allows better customisation in special cases. Addresses issue #206.
@frenya Thank you, I'll cherry-pick that so that you don't have to submit a new PR for the next branch. 😉 |
Thanks 👍 |
leMaik
pushed a commit
that referenced
this issue
May 13, 2018
Exporting defaultChipRenderer allows better customisation in special cases. Addresses issue #206.
@frenya v0.19.0 (one added keyword caused a minor version bump :D) was just released 🎉 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
would it be possible to export the
defaultChipRenderer
function inChipInput.js
? It would allow for easier customisation of chips in special cases.Example use case: Make the first chip non-deletable
Currently, I need to fully replicate the
defaultChipRenderer
including styles, colors etc. to be consistent. Exporting the renderer would make life much easier.Pretty please :)
Frank
P.S. I could make a pull request, but it's really just adding the "export" keyword.
The text was updated successfully, but these errors were encountered: