-
Notifications
You must be signed in to change notification settings - Fork 531
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
Adding Vue-Multiselect #21
Adding Vue-Multiselect #21
Conversation
Thanks! I will check your PR ASAP. |
Firstly, I think it is an optional field. So please remove it from dependencies in package.json. Instead load as an external component in the HTML like If PR is merged, I will update the docs, after I released a new version. Instead of docs, please make a test file for this multiselect field. Use the fieldSelectEx.spec.js as a boilerplate. You could write tests continuously with More comments I will add for your commits. Thanks for you work! For your two other questions:
|
closeOnSelect: true, | ||
// customLabel:function(){return ""}, | ||
taggable:true, | ||
tagPlaceholder:'Press enter to create a tag', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add an onNewTag
event handler to the selectOptions:
selectOptions {
...
onNewTag: function(...) { console.log(...); },
...
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also adding onSearch
(from onSearchChange
) since it is a very useful function (to create dynamics option list for country and all kind of filtering).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, great!
… loaded. Add it to dev files.
…om multiselect and update dev schema.
I will start the test later today, and also I will fix the linting |
Great thank you! |
@lionel-bijaoui when could you finish this PR? |
I'm working on it, but face a problem. I need |
Hmm, yes it's not easy. In this case, skip the unit test. If the main code is ready, commits and I merge it. After it I will try to make tests. |
The .jsbeautify is useful for my beautifier (it doesn't understand .eslintrc files). I have added a basic unit test and I hope the test will work (they worked locally). |
Thanks, Travis is green. 👍 |
I'm so happy right now 😄 |
Yes, it would be very good. Further conversation from css extraction here: #20 |
Hello,
This is my first ever contribution to an open source project, so please forgive me if I make mistakes.
Since you talked about adding vue-multiselect #18, I went ahead and begun to work on that.
I'm well aware this is not ready for pull request yet, but I wanted some guidance on were to go and what to change.
Obviously, I need to update the doc, but I would also like to talk about exporting some events from vue-multiselect to be exploitable in the schema definition. For example,
update
is the same asonChanged
, butsearch-change
ortag
don't have equivalent. Should we expose them ?Anyway, I tried to implement all basic options (props) from multiselectMixin.js, but I need to do the same for Multiselect.vue and pointerMixin.js.
I would also like to point a larger issues: i18n & styling. Should I create separate issues, or could we talk about it here ?
important
.I can see the benefits of having a ready to work version but maybe this vision of a css-less plugin should be exploited in a "lite" version of the plugin (vue-form-generator-lite) ?
Anyway thank for your help, I really need to make this plugin the best I can !