Vaadin Flow 6.0.10
Changes in Flow from 6.0.9
-
Fixes:
-
⧉ Add javadocs warning to avoid using ResponseWriter for dirs (#11112). PR:11164
-
⧉ Handle concurrent file requests (#11147). PR:11156. Ticket:11144
-
⧉ Set routes first into the template (#11107). PR:11126. **Ticket:**psi#26
-
⧉ Prevent passing bad character to wp (#11099). PR:11114
The webpack dev-server does not escape " character, as it is not valid URL. This limitation was not checked when passing request to it via DevModeHandlerImpl.
-
⧉ Use x64 version for mac for old nodejs (#11065). PR:11068. Ticket:11060
Use the x64 package for mac if the installed node version is < 16.0.0 as ARM package is not available before this.
-
⧉ Don't serve directories as static files (#11072). PR:11104
Add check to the resource to see if it is a directory and do not serve if this is the case. Fixe #11047
-
⧉ Annotate default error handlers. (#11063) (#11090). PR:11093
Annotate default error handlers with the new annotaton DefaultErrorHandler so that we can also in add-ons have default handlers that can be overridden by user handlers. Part of vaadin/spring#661 # Conflicts: # flow-server/src/main/java/com/vaadin/flow/router/InternalServerError.java # flow-server/src/main/java/com/vaadin/flow/router/RouteNotFoundError.java
-
⧉ Avoid NPE in query params parsing (#11075). PR:11095. Ticket:11019
A colon ":" in the location will not cause a NPE when parsing query parameters
-
⧉ Using a custom RouteRegistry (#11033). PR:11054. Ticket:11022
Make it possible to create a custom RouteRegistry and add test module for it.
-
⧉ Don't update cached extended details inside callback (#11043). PR:11049. Ticket:473
Makes fetching extended client details work for Multiplatform Runtime.
-