-
Notifications
You must be signed in to change notification settings - Fork 233
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
validate prop doesnt fire given function #177
Comments
same issues |
Yup just found this issue as well. I'll take a look and see if I can help any. |
I couldn't find an issue with the code. I cloned the repo and the validate method gets called as expected and the example shows a usage that is also working. I installed the latest latest from npm but still wouldn't work in my app. Then I used the code from the repo directly and it works. So it looks to me like the latest code hasn't been released to npm. |
@spirit Love you ! But i use another libary now ~ |
What do you use out of interest? I might have to switch as well. |
@incoqnito.io/react-tagsinput is the new version where the validation is built in (3.19.0) |
@olahol can you please release the correct version to the npm? the validate function is not working with 3.19.0 |
@olahol - The documentation and code are out of sync and unfortunately forces us to use another library. Please can you release the latest version to npm? |
@christianbirg - Good shout on using this library: https://www.npmjs.com/package/@incoqnito.io/react-tagsinput |
I'm using 3.19.0 and validate is not working, it only calls the onchange function. |
Bros, please use my library. I forked it and Push it to npm @incoqnito.io/react-tagsinput |
Thank you, i suppose the original library is no longer maintained.. |
Thank you. It works perfectly |
@olahol Hope you are well. Do you have time to release the latest version, please? My understanding is that the current version in the source control has already addressed this issue. |
latest version: I set tag => alert(tag) inside validate prop, but nothing fired
The text was updated successfully, but these errors were encountered: