Rename Valo to Lumo

[tomivirkki]

Change all mentions of Valo to Lumo. Make sure letter casing matches. Make sure theme/valo folder has been renamed. Depend on vaadin/vaadin-lumo-styles#^1.0.0 in elements

• vaadin-lumo-styles (make public and release 1.0.0-alpha1)
• vaadin-button
• vaadin-checkbox
• vaadin-combo-box
• vaadin-context-menu
• vaadin-core-elements
• vaadin-date-picker
• vaadin-dialog
• vaadin-dropdown-menu
• vaadin-element-skeleton
• vaadin-form-layout
• vaadin-grid
• vaadin-item
• vaadin-list-box
• vaadin-notification
• vaadin-ordered-layout
• vaadin-overlay
• vaadin-progress-bar
• vaadin-radio-button
• vaadin-split-layout
• vaadin-tabs
• vaadin-text-field
• vaadin-upload

[jouni]

I can take care of deprecating the vaadin-valo-styles package and repo (adding a console warning for users to migrate to vaadin-lumo-styles).

[fasihrana]

Will this take care of the Google Chrome Stylesheets HTML Imports Warning?

[Deprecation] Styling master document from stylesheets defined in HTML Imports is deprecated, and is planned to be removed in M65, around March 2018. Please refer to https://goo.gl/EGXzpw for possible migration paths.

[tomivirkki]

@fasihrana Not this particular change, but we're planning on fixing the warning issue during the ongoing alpha period.

[jouni]

@fasihrana see Polymer/polymer#5017 for more info.

Basically, the console warning is a false positive, the styling will still work. But with the small update, it should be possible to also avoid the console warning.

[jouni]

@tomivirkki could you add tasks for unregistering vaadin-valo-theme from Bower and registering vaadin-lumo-styles.

Update: I drafted the deprecation message for the previous package, and stated that the package and repo would be removed “after March 2018”. Does that sound alright?