Leif Åstrand

This probably means that the listener is run without `access` and might thus also cause other interesting issues.

This is a side effect from the fact that `Column` extends `Component` and we have opted to make `Component` implement `HasStyle` since 99% of all components do support styles in...

I wonder if we might be hiding some potential "actual" state management issues if we would suppress this error? Might be a smaller problem to throw at those who mess...

One challenge with Variant 1 is the way the production build needs to know which imports will be used so that it can know what to include in the frontend...

I believe that OSGi metadata is the only change. Maybe @tsuoanttila or @Artur- can confirm? If that is the case, then it seems like the changes would be quite compatible....

Turns out that version `2.8.2.vaadin1` is slightly broken in the way that it accidentally also depends on the upstream `2.8.2` module. As a workaround for now, the additional dependency needs...

Yes, but that will require some additional effort because of the way `2.8.2.vaadin1` has been made. There's https://github.com/vaadin/flow/issues/4598 for eventually creating a more sustainable solution.

We are planning to add support for an automatic main menu also for Flow layouts and we wouldn't want to have parameterized Hilla routes in the Flow menu either. From...

Views with optional parameters should be in the menu except if excluded using the regular mechanism. It's only the ones with required parameters that must be left out since we...

Seems like this is "only" broken for the case when the parameter is in the directory name. `views/test/{id}.tsx` does not show up in the menu but `views/users/{id}/edit.tsx` does.