Mikhail Shabarov

Access control seems to work fine for Flow view. 1) Navigating from Hilla view to protected Flow view reroutes to login view if not authenticated. 2) Navigating from Hilla view...

@MeftunH could you please give us the Vaadin and Spring versions that you use and possible an example project that we can use to reproduce it ?

Done. Tested with having `vaadin` and `vaadin-core`. Vaadin adds `react-components-pro` in the first case and does not in the second case.

For reference, these two issues should cover these last urgent changes: https://github.com/vaadin/platform/issues/5204 https://github.com/vaadin/platform/issues/5260

An alternative solution is proposed here https://github.com/vaadin/hilla/pull/2383. This PR may become a refactoring PR that doesn't move `hilla-dev`, but just splits `vaadin-dev` into two artifacts.

This refactoring was proposed to start when we are ready for bigger changes or we have a request from users earlier with a good reason to split to `vaadin-dev-flow` and...

@roeltje25 thanks for the issue. Yes, we are thinking how we can fix it on our side and avoid extra annotations.

The problem with bean discovery mode is a bit wider: without setting it to `all` Vaadin applications end up with views not discovered as CDI beans even if they have...

I personally don't have enough expertise to decide to include AtStereotype or not. This is not a priority at the moment for Flow team. Let us keep this in a...

This issue should be fixed by adding `refreshAll()` method call to the filter (and sorting maybe) methods in `DataView`.