vaadin / vaadin-board-flow

Flow integration of vaadin-board

Vaadin web components

This package contains all Vaadin web components (free and commercial).

See https://github.com/vaadin/web-components for more details.

vaadin-board-flow's Issues

Problem in Vaadin 14 (npm mode) with @HtmlImport annotation inhertied by clients

2019-10-28 17:48:10,337 ERROR [com.vaadin.flow.component.internal.ComponentMetaData] (default task-2)
de.mach.selfservices.ui.components.layout.MachRow has only @HtmlImport annotation(s) which is ignored in Vaadin 14+. This annotation is only useful in compatibility mode. In order to use a Polymer template inside a component in Vaadin 14+, @jsmodule annotation should be used. And to use a css file, {@link CssImport} should be used. If you want to be able to use your component in both compatibility mode and normal mode of Vaadin 14+ you need to have @HtmlImport along with @jsmodule and/or @CssImport annotations.Go to Vaadin 14 Migration Guide (https://vaadin.com/docs/v14/flow/v14-migration/v14-migration-guide.html#3-convert-polymer-2-to-polymer-3) to see how to migrate templates from Polymer 2 to Polymer 3.
2019-10-28 17:48:10,337 ERROR [com.vaadin.flow.component.internal.ComponentMetaData] (default task-2)
com.vaadin.flow.component.board.Row has only @HtmlImport annotation(s) which is ignored in Vaadin 14+. This annotation is only useful in compatibility mode. In order to use a Polymer template inside a component in Vaadin 14+, @jsmodule annotation should be used. And to use a css file, {@link CssImport} should be used. If you want to be able to use your component in both compatibility mode and normal mode of Vaadin 14+ you need to have @HtmlImport along with @jsmodule and/or @CssImport annotations.Go to Vaadin 14 Migration Guide (https://vaadin.com/docs/v14/flow/v14-migration/v14-migration-guide.html#3-convert-polymer-2-to-polymer-3) to see how to migrate templates from Polymer 2 to Polymer 3.
2019-10-28 17:48:10,339 ERROR [com.vaadin.flow.component.internal.ComponentMetaData] (default task-2)
de.mach.selfservices.catalog.ui.TilePreviewPage has only @HtmlImport annotation(s) which is ignored in Vaadin 14+. This annotation is only useful in compatibility mode. In order to use a Polymer template inside a component in Vaadin 14+, @jsmodule annotation should be used. And to use a css file, {@link CssImport} should be used. If you want to be able to use your component in both compatibility mode and normal mode of Vaadin 14+ you need to have @HtmlImport along with @jsmodule and/or @CssImport annotations.Go to Vaadin 14 Migration Guide (https://vaadin.com/docs/v14/flow/v14-migration/v14-migration-guide.html#3-convert-polymer-2-to-polymer-3) to see how to migrate templates from Polymer 2 to Polymer 3.

Please can you fix asap?

version should be 2.0-SNAPSHOT

Update to Flow Beta 12

Not in BOM of commercial components?

<groupId>com.vaadin</groupId>
            <!-- Replace artifactId with vaadin-core to use only free components -->
            <artifactId>vaadin</artifactId>

So when when I use this "commercial" variant with version 14.0.11 I have to add a version number and a dependency on vaadin-board-flow.

Generate OSGi metadata

Do not use Charts in Board integration tests

Using vaadin-charts in integration tests here doesn't make much sense to me.

It introduces problems with reference screenshots regularly when new Firefox / Chrome version is released. So for example the differences can be as follows:

We should update all the tests to use colored boxes using div etc.

Update to Flow rc2

Copyright and license is missing from file headers

Generate OSGi metadata