Leif Åstrand

The comparison with Spring Boot is interesting even though I don't think it's fully comparable since we don't aspire to even get close to the same breadth. At the same...

> com.vaadin:vaadin - the big ball of everything (not sure who needs it) I think that's the key to solving this puzzle. The `vaadin` and `vaadin-core` dependencies are really relics...

The `Version` class exists from ancient times. There's probably lots of existing code out there that relies on it so we would probably break stuff if we'd just change it....

I don't think an interface is the right option since interfaces define the public API of a class and you wouldn't want to make methods like `setState` part of the...

The implementation of `ReactAdapterComponent` is basically just some helpers around `Element::setPropertyJson`, `Element::getPropertyRaw` and `Element::addPropertyChangeListener`. All of the actual magic is handled by Flow and/or the client-side base class for the...

The application contains a `@Route(value = "/:samplePersonID?/:action?(edit)")` view and the main problem is that this URL is added as-is to the menu even though you cannot navigate to that URL....

I wouldn't be surprised if this is just the way some browser implementations work and there's nothing we can do about it.

The menu title does not necessarily have anything to do with the page title, especially in the case of `HasDynamicTitle` and views that aren't even directly shown in the menu....

The metadata is known at compile time for Hilla views but it's only known after a round trip for Flow views. (Though there's also the question on how to implement...

That sounds like a hack even though it would in one way also solve the related problem of how Hilla views would update the title shown in the layout in...