vaadin/flow 0.1.6

Production mode and bugfixes

on GitHub

New features

• When not in production mode, frontend:// URLs will be resolved based on the assumed location of the original file instead of resolving to a URL in /es6/ or /es5/. Thanks to this, changes to the application's own template files are used immediately without any separate build steps.
• New flow-server-production-mode dependency that automatically sets the app to run in production mode if present on the classpath.

Fixes

• All traces of Polymer 1 have been removed.
• Model objects exposed to JavaScript are created with the standard Object prototype so that e.g. toString is available.
• Model objects exposed to JavaScript will no longer have enumerable properties for Flow metadata.
• Removed excessive logging about excessive imports.
• Fixed an IE11 compatibility issue
• The UI.getElement() now works as any other element.

Breaking changes

• com.vaadin.flow.dom.EventRegistrationHandle has been renamed to com.vaadin.shared.Registration for consistency with Vaadin Framework 8.
• Node.attachExistingElement has been removed.
• Prerendering has been removed

Demos

• All demos updated to not need rebuilding to pick up changes to HTML template files

Tutorials

• Updated Maven setup tutorial to reflect recent changes

All changes

https://github.com/vaadin/flow/milestone/33?closed=1