-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
meta flag issue with vue v3.2.0-beta.x #3407
Comments
It doesn't look like a reactivity issue as I noticed there is an extra validation run that was being run at the end of a reset state call and making those 2 tests fail, but reactivity-wise it seems to be working as expected. Found a workaround to avoid it, but no clue what is causing it. I Will do a quick tag. |
@cexbrayat I Tagged |
Thanks for looking into this! Sadly not yet. I put together a small repro cexbrayat/vue-v313#3 The component is <Field name="name" rules="required" v-slot="{ field, meta }" v-model="user.name">
<label for="name-input" :class="{ 'text-danger': meta.dirty && !meta.valid }">Name</label>
<input id="name-input" :class="{ 'is-invalid': meta.dirty && !meta.valid }" v-bind="field" />
</Field> and the problem is quite weird: |
Doesn't look related to vee-validate, the class binding seems to get borked for some reason On a quick hunch, if you make the class binding after the <input id="name-input" v-bind="field" :class="{ 'is-invalid': meta.dirty && !meta.valid }" /> Probably worth reporting in the Vue repo |
Good catch! I managed to repro without vee-validate 👍 |
What happened?
Looks like some tests are failing in 3.2.0-beta.x releases related to meta flags
reported originally in #3400 by @cexbrayat
Reproduction steps
yarn test
Version
Vue.js 3.x and vee-validate 4.x
What browsers are you seeing the problem on?
Relevant log output
No response
Demo link
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: