Thorsten Lünborg
Thorsten Lünborg
You're watching the wrong thing, I'd say. Watch the URL generated by router.resolve: ```ts watch(() => router.resolve({ name, params, query, }).href, (newUrl, _, onCleanup) => { const abortController = new...
My linked comment is incorrect as it relates to triggerRef. I was, at that moment, more focused on the asynchronous execution of the test. Further down in the linked issue'S...
That example works as expected. Triggering the `obj` ref makes the computed re-evaluate, but since it returns the same value, that will not trigger a rerender of the template. If...
For now, just use `?:` in the prop type to make the prop optional. Also allows for rhe prop to be undefined. ```ts const props = defineProps(); ```
When and where exactly is that error being raised? Do you also get an error in VSCode/your IDE? As an experiment, try this please: ```ts const props = defineProps any...
Okay, so I can kinda reproduce this, but a full repro from your side in a github repo would be apprechiated to make sure we are looking at the same...
That's because in your example you are essentially casting all 4 objects to be of type `Prop`. They don't have their own explicit type that could clash with your `:...
@pikax So there's two layers to this: 1. **Runtime/codegen**: There's the problem of code generation: an `optional?:` prop generates a proper runtime prop definition, while a prop with `x |...
When you go from home back to about, the `About` component is mounted again, so it adds the attribute again. Works as you designed it to work. ~~1. Vue re-uses...
See my edited comment, misunderstood your problem.