Vue-form-generator: Using v-if and v-for on the same element is not recommended

Created on 29 Sep 2016 · 8Comments · Source: vue-generators/vue-form-generator

Currently getting the error in the title.

Full error:

vue.common.js?4a36:1137[Vue warn]: <div v-for="field in fields" v-if="fieldVisible(field)">: Using v-if and v-for on the same element is not recommended - consider filtering the source Array instead. (found in component: <vue-form-generator>)

Am I doing something wrong?

bug

Source

Cannonb4ll

Most helpful comment

I don't think you did anything wrong, this is something we missed. We never got this message on our dev environment, because we were using "vue": "1.0.26".
I just updated "vue": "1.0.27" and I got the same message. So this is new and we need to change the way it work.
You don't need to worry too much about this message for now, and we will fix it.
Thank you for your feedback

lionel-bijaoui on 29 Sep 2016

👍2

All 8 comments

lionel-bijaoui on 29 Sep 2016

👍2

Then I experienced the same issue, I did an npm update yesterday and with that some new versions came along. Ever since this warning occured.

Application works just fine though, will be waiting for a update, take your time 👍

Cannonb4ll on 29 Sep 2016

Just be careful if you use it in production, this is still technically an alpha (v0.x.x) and API may change a lot.
This is why feedback from user like your is very valuable.
You can also spread the word about this plugin.
We need help for accessibility related issue #74 , and we don't have any experience about it. Someone who know about this would be super helpful. Just saying !

lionel-bijaoui on 29 Sep 2016

👍1

I have been sharing this plugin a lot, actually haha. Didn't knew it was in Alpha! I am planning on using this plugin in a production environment, not a big application but it works just fine to be honest.

I will be looking into your issue as well when I get the time. (#74)

Cannonb4ll on 29 Sep 2016

👍1

Thank you !
Don't worry, every release is working, it just that between release, big change might be introduced. We try to minimized that, but we can't guaranty it.

lionel-bijaoui on 29 Sep 2016

It is alpha, but working :) We have break changes in releases. So if you would like to use in production, we recommend to lock the version in package.json and update only manually.