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

Issue with v-model data when selectedTags is empty #43

Closed
lainga9 opened this issue Jan 30, 2019 · 6 comments
Closed

Issue with v-model data when selectedTags is empty #43

lainga9 opened this issue Jan 30, 2019 · 6 comments

Comments

@lainga9
Copy link

lainga9 commented Jan 30, 2019

If the component is initialised with an empty array set for the v-model then when a tag is added and the tags-updated or tags-added is fired, the v-model array still remains empty.

I've tried cloning this repo and modifying your demo example and the problem still remains.

So if you were to update the selectedTags property to be an empty array and in your onTagAdded or onTagUpdated callbacks you console.log(this.selectedTags) you will see an empty array the first time you add a tag. If you delete the tag and then re-add the console will correctly show the array with one item in it.

Any thoughts?

@mitsuru793
Copy link

mitsuru793 commented May 8, 2019

Me too. I see this problem when first adding a tag.
I use the event tags-updated.

@AlexMordred
Copy link
Member

Hey. Sorry for the late reply. I just released a new version and I was unable to reproduce the bug there. Please give a try again. Feel free to reopen this if the bug persists.

@marylein
Copy link

I have the same issue with the new version. The first tag is not showing up in the selectedTags, as soon as I add a second tag, the array will be shown correctly.

@shiwangebuzhidao
Copy link

I include this library into my page manually from a CDN, I already use the latest versio but the first time when I added a tag, the selectedTags is empty array and array is correct when I added a second tag.

@AlexMordred AlexMordred reopened this Jul 24, 2019
@fabriguespe
Copy link

same here!

@AlexMordred
Copy link
Member

Thanks guys! This has been fixed in v.2.0.2.

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

No branches or pull requests

6 participants