Comp API + Vuetify + Reference = ♾ update loop

[Stoom]

Version

1.0.3

Subject of the issue

It looks like if you add a ref to any Vuetify component (I tested VForm, VBtn, and VCard) with @vue/composition-api then it displays the infinite update loop message and fails the test.

[Update]:
It looks like it has to do with updating the input and having a ref. If you remove the ref to the button or the v-model on the input the error goes away. I'm pretty sure that the v-text-field uses requestAnimationFrame as well.

Steps to reproduce

<template>
  <v-form>
    <v-text-field v-model="name"></v-text-field>
    <v-btn ref="foobar">
  </v-form>
</template>

<script lang="ts">
  import { defineComponent, ref } from '@vue/composition-api';

  export default defineComponent({
    setup: () => {
      const name = ref('');
      const foobar = ref<HTMLElement>(null);
      return { name, foobar };
    }
  });
</script>

Expected behavior

The tests to pass with no warning

Actual behavior

[Vue warn]: You may have an infinite update loop in a component render function.

found in

---> <TestComponent> at src/components/TestComponent.vue
       <Root>
      1) Should be enabled when valid

Possible Solution

Most likely related to #1407 ?

[lmiller1990]

There are a lot of ways to trigger an infinite loop in Vuetify testing, for some reason. I think you are right that #1407 is related. I do not think this is related to the Composition API.

This is a very interesting reproduction, it is much more minimal than the #1407 one. I guess we need to dive into Vuetify.

I wonder if opening an issue on Vuetify might get some more action on this?

[Stoom]

I can file a bug report over there as well. Do you think if there wasn't composition API that removing there ref would still fix this?

[lmiller1990]

Unlikely... you should be able to try it out easily though and find out. I think this is related to the odd way that Vuetify creates components (using many mixins and the such). I don't have a good reason why, but no other library has this problem, and there have been other weird bugs historically that were related to heavy use of mixin and extends.