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
Vue.js 2.0 support #56
Comments
Currently I hate the new v2.0 version of vue :) Evan killed the best features of VueJS what I like. 😠 By the way, I don't think, it is a neccessary feature. Because we publish a bundle version what contains the vuejs too. So (I think, but need to test) vue-form-generator can be used in a Vue 2.0 project. Do you feel like to test it? |
I think this new version is awesome. Most change come from good reasons and Le 30 août 2016 12:06, "Icebob" notifications@github.com a écrit :
|
So I think you can use vue-form-generator in a Vue 2.0 project. The lib won't use Vue 2, because bundle contains the Vue 1.0.26. Check here. If you want to test it, fork the example fiddle and change the vue external link to v2 and change the js code to be compatible with v2. |
Filter are back ! Usage is limited to interpolation only, but it is were
they should be used (syntax changed for the better too).
Also, converting from .sync to @event is more work, I totally agree, but it
helps clarify where the change come from.
I'm not sure what formatters are.
I'm a bit busy right now, but I will try to test things out.
|
My thinking was wrong. 😞 It doesn't work. https://jsfiddle.net/icebob/8neaa2vo/1/ |
@icebob We are switching to vuejs 2.0 at my company so I need to adapt vue form generator to it.
I'm taking care of the changes and I will do a PR later. |
I prefer to make a |
I had such a hard time, bugs everywhere nothing was working, it was hell... For now I will not get trigger happy and change everything, but having two way of writing is inconsistent. The risk of other bad surprises demand a decision in the long run. Other than that, I'm fixing bugs, updating libs and adapting everything. I will need your help to update the dev app (the one that save and load fake profiles). |
@icebob can you create the branch |
I don't understand why has problem with jade. Currently has similar expressions in jade and there is no problem with webpack. You are only change VueJS v1.0 to v2.0, aren't you? |
The loader are updated too. Vuejs v2.0 transform the template into render functions with webpack. |
I have problem with noUiSlider, selectEx, and vue multiselect. Also, the dev app is not working well, and the validator is weird. Some behavior have changed and things update faster which may or may not be the cause. |
I think it is a bigger project to rewrite all codes to v2. And tonight I added some commits to both branches, so you need to merge them too 😞 Are there any other solution, that you can use the current version of VFG in your Vue2 project without rewrite all stuffs? Because I don't know that I will have enough time to help you to fix all v2 issues quickly. Other question: Can we make the migration that it will working with Vue1 & Vue2 the same code? Because I don't plan yet to change Vue to v2 in my projects. |
P.S: Get well soon! |
@lionel-bijaoui Today I fixed validators and unit tests. Now test is green 🎉, but there are 10 skipped. |
@icebob wow congratulations ! Keep up the good work ! |
Just tried 2.0.0 beta. multi-level object doesn't seem to be working. |
I am using the beta 2.0 for a project. Thanks for the updates. Would like to mention that the validation didn't seem to work for me. pikaday also didn't work. |
@amanpatel What is the problem with validation? |
Just didn't do anything. I had set required:true in the schema, and upon submission no flags came up, (or even onBlur when value was empty). |
And do you set validators in schema, like here ? |
@xumx issue is fixed in beta3 |
|
Congratulation !! Sorry that I was not available to help. |
No problem :) |
I guess it going to be hard to do, but this is something necessary.
2.0 changes
No more
.sync
My first analysis point to one real problem, the disappearance of
.sync
.so instead of:
We should do:
and inside the fields (abstractField.js)
Also change formGenerator.vue:
to
This need to be tested.
Change in hook
Another thing could be related to
ready
becomingmounted
. There's no longer the guarantee to be in-document and could break most js dependent fields.We should test if the component is in document ourself now. I have no idea how to do that.
Maybe check if
vm.$el
have a parent ? And if not use a small setTimeout to lauch the test again soon ?I'm sure I'm missing a lot of problem, but this seem achievable.
What are your thought ?
The text was updated successfully, but these errors were encountered: