Leif Åstrand

With `src` being `null` or `undefined`, `` behaves as though the `src` would be `"null"` or `"undefined"` respectively, thus causing a request to an URL that most likely doesn't return...

@ernsheong That approach works nicely when you have 200 items all in all and need to generate and populate 180 empty objects. It breaks down when you have 10 000...

Should be possible to do this automatically based on the routing metadata that is included in the index HTML document. We should just take care to make the decision based...

The default should be to render server-side views in the top-level `$layout` but it should also be possible for the application developer to inject `...serverSideRoutes` into some other part of...

> and dynamically update import of this file in `Flow.tsx`. I guess this is related to the circular dependency that we discussed? We cannot make _any_ assumption about what will...

I guess we would want to reuse some existing library for this rather than building our own?

I would still encourage using a library from the beginning to avoid causing regressions if we later on switch to using a library that isn't 100% compatible with our own...

I suggest we fix this by changing examples to reload the page after logging in. The reason for this is that it's not uncommon that you also want to change...

> based on `DeplymentConfiguration`'s method called `isReactEnabled`. That won't be reliable in the case of application that use both Lit and React side-by-side since the current idea of how to...

I suspect `isReactEnabled()` is wrongly named. It should actually be `isLitDisabled()` instead. I wonder if the logic should be such that if `@vaadin/react-components` is present in `package.json`, then we consider...