Another mini rant about the vibecoded project I'm fixing.
-
Another mini rant about the vibecoded project I'm fixing. :wvrnFlat:
So we use Vue. For bidirectional data flows between components, you use the modelValue prop and update:modelValue event, which can nicely be used via v-model. The colleague didn't do that, of course. He added a prop like task and an event like update (without any parameters), and then he mutated the task prop directly. THIS IS NOT WHAT YOU SHOULD DO, EVER -
Another mini rant about the vibecoded project I'm fixing. :wvrnFlat:
So we use Vue. For bidirectional data flows between components, you use the modelValue prop and update:modelValue event, which can nicely be used via v-model. The colleague didn't do that, of course. He added a prop like task and an event like update (without any parameters), and then he mutated the task prop directly. THIS IS NOT WHAT YOU SHOULD DO, EVER -
@Erpel
-
Another mini rant about the vibecoded project I'm fixing. :wvrnFlat:
So we use Vue. For bidirectional data flows between components, you use the modelValue prop and update:modelValue event, which can nicely be used via v-model. The colleague didn't do that, of course. He added a prop like task and an event like update (without any parameters), and then he mutated the task prop directly. THIS IS NOT WHAT YOU SHOULD DO, EVEREvery single edit in that component — and there are many — is likeprops.task.someArray.push(...) emit("update")
AAAAAA
-
Another mini rant about the vibecoded project I'm fixing. :wvrnFlat:
So we use Vue. For bidirectional data flows between components, you use the modelValue prop and update:modelValue event, which can nicely be used via v-model. The colleague didn't do that, of course. He added a prop like task and an event like update (without any parameters), and then he mutated the task prop directly. THIS IS NOT WHAT YOU SHOULD DO, EVER@volpeon Ah but you see, does it anyway
-
@volpeon Ah but you see, does it anyway
-
Every single edit in that component — and there are many — is likeprops.task.someArray.push(...) emit("update")
AAAAAA @volpeon i recently replaced passing callback function as prop with proper event from some ancient code in pleromafe... -
Every single edit in that component — and there are many — is likeprops.task.someArray.push(...) emit("update")
AAAAAA He's even mutating the prop IN A GETTERconst thing = computed(() => { if (...) { props.task.prop = {...}; emit("update"); } });
-
He's even mutating the prop IN A GETTERconst thing = computed(() => { if (...) { props.task.prop = {...}; emit("update"); } });
@volpeon@icy.wyvern.rip
emit("volpeon:mad") -
Another mini rant about the vibecoded project I'm fixing. :wvrnFlat:
So we use Vue. For bidirectional data flows between components, you use the modelValue prop and update:modelValue event, which can nicely be used via v-model. The colleague didn't do that, of course. He added a prop like task and an event like update (without any parameters), and then he mutated the task prop directly. THIS IS NOT WHAT YOU SHOULD DO, EVER@volpeon@icy.wyvern.rip why is it called vibe coding when the vibes are absolutely atrocious
-
Every single edit in that component — and there are many — is likeprops.task.someArray.push(...) emit("update")
AAAAAA @volpeon@icy.wyvern.rip I am enjoying this series of events. This is fun to read but likely a nightmare to work on.
-
He's even mutating the prop IN A GETTERconst thing = computed(() => { if (...) { props.task.prop = {...}; emit("update"); } });
Fucking hell, how am I even supposed to salvage this
