-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
Allow users to create new if not found #432
Comments
Hello @noctivityinc, Thanks for your suggestion! I'll make sure I got you right. You're looking forward to customizing the no-results condition by adding actions. You can do that through the Have a nice day! |
@TarekRaafat worked great, thanks! |
@TarekRaafat I spoke too soon. While it DOES work to let me trigger an event to create a new item, there doesnt appear to be a way for me to refresh the data attribute with an updated source so that the new item appears the next time the user searches the list. For example, assume this flow:
I COULD create a new dom element and add it to the list, but that doesnt change the What we need is something like `autoComplete.append([{id: 123, name: 'New Item'}]) that would let us add something new to the list and then refresh the data. Any thoughts? |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
No. The library is amazing!
Thoroughly Describe the solution you'd like
A clear and concise description of what you want to happen.
Im surprised I dont see this already in here as it's pretty standard for tags and the like. If the user types something that doesnt exit, I need there to be an option to "Add _____ as new tag" that would then submit a function with the value.
Please provide a few use cases for this feature
Please Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I can add a small + button NEXT to the list to create a new option, but that's not nearly as efficient in the workflow
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: