Component generator demo and metadata, URI resolving from JavaScript, and HTML imports in the initial HTML

New features

• Component API generator enhancements
  • Added a flow-components-demo module that shows how the generated APIs are used
  • Updated to use Polymer Analyzer 2.0
  • Added metadata to generated classes, e.g. @HtmlImport, @Tag, JavaDocs, license header and version information
  • baseUrl setting is considered when determining the Java package of a generated class
• @Id can be used for Element fields in addition to previously supported Component subclasses.
• Server-side component instances are automatically created for corresponding elements in the HTML of PolymerTemplate instances.
  • Still only limited functionality, doesn't work together with e.g. <dom-repeat> or <dom-if>.
• The webcomponents polyfill is loaded from the application's own bower_components directory instead of using an (outdated) version bundled with Flow.
• Added window.vaadin.resolveUri for resolving Vaadin URIs from JavaScript.
• Non-lazy HTML imports encountered during the initial request are added directly to the initial HTML instead of being injected dynamically from JavaScript.

Fixes

• Hyphens and underscores are properly converted to camelCase in generated code.

Breaking changes

• Initial HTML imports will be loaded at an earlier phase than previously. This will cause issues e.g. if the HTML import assumes that document.body is defined.

All changes

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