You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting an app with Vaadin 15 I want the default mode for views and bootstrapping to be client-side (index.html / index.ts + client-side routing + TypeScript views) so that it's easy to try out new features added in V15.
Note: Vaadin recommends to use the latest long-term support (LTS) version in any production project. V15 is not an LTS version, thus it's OK to make an experimental feature the default option there. It's still possible to change this default by adding the -Dvaadin.clientSideMode=false system property.
DoD:
If the vaadin.clientSideMode property is not set, it's assumed to be true by default and the bootstrap happens using IndexHtmlRequestHandler instead of BootstrapHandler.
The Vaadin Platform snapshot that includes the version of Flow with this change passes the build.
First and foremost that includes updating all starters listed in the Update maven starters build. Each starter needs to run in the default mode (without requiring the -Dvaadin.clientSideMode=false flag). It's enough if routing remains fully server-side and the change only concerns the bootstrapping.
This PR sets the clientSideMode as the default mode of the application.
To be able to use server-side bootstrap (v14), vaadin.clientSideMode must be false
Connected to #6367
When starting an app with Vaadin 15 I want the default mode for views and bootstrapping to be client-side (
index.html
/index.ts
+ client-side routing + TypeScript views) so that it's easy to try out new features added in V15.Note: Vaadin recommends to use the latest long-term support (LTS) version in any production project. V15 is not an LTS version, thus it's OK to make an experimental feature the default option there. It's still possible to change this default by adding the
-Dvaadin.clientSideMode=false
system property.DoD:
vaadin.clientSideMode
property is not set, it's assumed to betrue
by default and the bootstrap happens usingIndexHtmlRequestHandler
instead ofBootstrapHandler
.First and foremost that includes updating all starters listed in the Update maven starters build. Each starter needs to run in the default mode (without requiring the
-Dvaadin.clientSideMode=false
flag). It's enough if routing remains fully server-side and the change only concerns the bootstrapping.The text was updated successfully, but these errors were encountered: