UI navigation

Flow
1

Hi Vaadins,
it seems there are different solutions to navigate programmatically via UI.navigate. But what is the difference between the two different versions? One preferred over the other? Thanks for some explaining words.

        grid.asSingleSelect().addValueChangeListener(event ->
                UI.getCurrent().navigate(FlightDetailsView.class, new RouteParam("flight-id", event.getValue().getFlightId()))
        );

        grid.asSingleSelect().addValueChangeListener(event ->
                grid.getUI().ifPresent(ui ->
                        ui.navigate(FlightDetailsView.class, new RouteParam("flight-id", event.getValue().getFlightId()))
                )
        );
2

They all end up calling the same method. Choose what is better for your code.

3

Or are you talking about how to get the UI?

4

No exactly. Then I use the optional-free, static version. Thanks!

5

Use UI.getCurrent() if you are sure the code is executed in a Vaadin request

6

this is usually true for component listener, unless you are doing updates in a background thread without using UI.access() (in this case you should always store a UI reference and execute the update action in an UI.access call)

7

They all end up calling the same method. Choose what is better for your code.
Just for clarity, I was talking about the navigate method here, not about getting the UI instance

8

Thanks @versatile-zorse for clarification. Now I got it. :slightly_smiling_face:

9

How about this enhancement :thinking: ComponentEvent should expose UI · Issue #18818 · vaadin/flow · GitHub