Reinier Kaper

Because you can have multiple of the same type of fields. Maybe I could use their ID's in that case instead?

So this is where I get confused. How does the model update the `valid` part? I thought it only update the value? ``` this.$emit({ value: event.target.value, valid: someValidationMethod(this) }) ```...

Just to add some context, this is what I could do previously: ``` js computed: { isReady() { return this.$refs.email.isValid && this.$refs.password.isValid } } ``` But now I need to...

Sure go for it! Thanks for the discussion guys, it;s appreciated. Vue is an amazing framework and the open conversations around it make it only better ;)

Alright, at least your example works. Now with the added state, the real issue is the combination with Vuex. Since the Vuex getters aren't yet available when the state is...

Here's two repos that compare the two scenarios: Vue1: https://jsfiddle.net/okv0rgrk/8330/ Vue2: http://jsfiddle.net/5sH6A/744/ I hope this clearly illustrates the current problem. The biggest issue right now is the fact that you...

The only workaround for this, is to supply the variables when calling the mutation manually, e.g.: ```ts const { mutate } = useMutation(LOGOUT) const doThing = () => mutate({ input:...

The following also seems like a TS bug: ```ts const variables = ref({ // same issue for `reactive` instead of `ref` input: { id: 'test', }, }) const { mutate:...

To add to this: it gets even worse when you have blocks of PHP in your HTML. They'll be forced to the start of the line, instead of keeping proper...

It's still showing up, but I'm not sure if there's a newer version, will check that later. We also get an "app quit unexpectedly" warning whenever we close Cypress.