R&D decisions (deleted from prev repo)

[dy]

<define-element> vs <template is="define-element">

• <define-element> misses useful declaration-by-example - tagname, extension, proptypes, enforces module exports.
• <template is="define-element"> has clumsy implementation, uncertainty if tag is declared or reused as content, conflicts with immediate template (shadow-root="open" etc), makes uncertain scope of template parts.
• <element-defs> inspired by SVG <defs> is graceful mix, excluding drawbacks of both.

export default propTypes, export let x = 1 for parts

• Live bindings are module resolution mechanism, should not be overused
• export default entails ungracious parsing and inline module resolution mechanics

[dy]

to calc or not to calc?

Some css-like variables would come handy. But what's the syntax/method?

• <svg left:="{{ a * b }}">, <svg left:calc="{{ a * b }}">
  • no established pattern of declaring template parts that way
• <script scoped>for await (let props of this.props) { this.props.y = props.x * 2 }</script>
  • always available
  • can be unclear
  • full math is available, unlike in calc
• declare in props via calc as <my-element left="{{ a * b }}">(\
  • confused with regular props
• attributeCallback - that's very normal to react on property change, so reuse that. :star: