Thorsten Lünborg comments

Results 351 comments of


                                            Thorsten Lünborg

trafficstars

Update slot content without rerendering rest of component

> I wonder if this can be reasonably detected. Hardly, and if so, only during compile time, not runtime. That would require some analysis during compilation that would have to...

Update slot content without rerendering rest of component

Yes.

Update slot content without rerendering rest of component

> We have a lot of forms where the structures are defined by a json document on load, this does mean that the slots are dynamically defined (even if they...

Update slot content without rerendering rest of component

Would be helpful to have some. Up-to-date example that demonstrates the effect, especially with the new slot syntax. From what I've read I don't entirely get the problem.

Update slot content without rerendering rest of component

I see what you mean but I don't really see a via able way to accomplish this except *not* using a virtualDOM, which means writing a new framework, essentially. You...

Update slot content without rerendering rest of component

I'll answer aboutbrh why tomorrow, it's 1am here. But as I see a risk of us talking past each other I would *still* be thankful for an actually runnable example...

Update slot content without rerendering rest of component

Aside from the optimizations we already introduced to Vue 2 with `v-slot`: No. VirtualDOM implementations rely on this behavior in general. Vue 3 is no different. Vue 3 might offer...

feat(compiler-sfc): [BREAKING] default `<script>` lang option for parser

I have my a doubts about this change - not about what it does (I think it makes sense), but when to introduce it. It feels like a breaking change...

fix(runtime-dom): ensure element attributes are always properly applied regardless of being passed in kebap-case or camelCase. (fix #5477)

@yyx990803 This is my second attempt at tackling this. You wrote in my previous PR it would not be the right fix as it would conflict with SVG attributes, but...

When accessing the hasOwnProperty method of the array, the key cannot be tracked

that's not a solution to the issue ...