Update the documentation to refer to Lit in all parts and not refer to Polymer in examples

[pleku]

The documentation should not refer to Polymer anymore in any examples and the docs should be highlighting the approach of having layouts in html/js and UI logic in Java:

• creating a web component documentation https://vaadin.com/docs/v17/flow/web-components/integrating-a-web-component.html
• "creating polymer template" (should be named something else already for 17) should not have examples for Lit which then import polymer like https://vaadin.com/docs/v17/flow/polymer-templates/tutorial-template-basic.html
• The component add-on starter should be not based on a Polymer component https://github.com/vaadin/component-starter-flow either using a VanillaJS web component or maybe a lit based web component
• The reading of initial attribute values for template mapped components to server side memory should be clarified in https://vaadin.com/docs/v17/flow/polymer-templates/tutorial-template-intro.html#known-limitations-of-templates
  • The attribute values are by default set as properties, except for certain standard attributes like id, style, class, theme, disabled
  • It should explain what limitations there are, like changing text content will replace all child elements

[joheriks]

Do we plan to upgrade the component starter to integrate a Lit component instead of a Polymer one? It is linked in the documentation on integrating a web component.

[pleku]

Do we plan to upgrade the component starter to integrate a Lit component instead of a Polymer one? It is linked in the documentation on integrating a web component.

It is the third point in the AC ?

The component add-on starter should be not based on a Polymer component https://github.com/vaadin/component-starter-flow either using a VanillaJS web component or maybe a lit based web component

[joheriks]

Yes, I noticed, but is it part of this ticket to do the actual modification of the starter?

[pleku]

Yes it was discussed as such, but I think it is fine if you want to split it out.

[joheriks]

Split out to ticket vaadin/npm-addon-template#236. I suppose mwc-slider would be a reasonable substitute.

[joheriks]

Just checking: does this part

It should explain what limitations there are, like changing text content will replace all child elements

refer to the situation where the template is e.g.:

      <div id="myDiv">
        <vaadin-button id="myButton">VButton</vaadin-button>
      </div>

and doing myDiv.setText("abc") in the Java side causing the myButton child to disappear, or something else?