Investigate functional components about destiny

[ebebbington]

@0kku coming from a react background, this approach seems nice and I guess it feels cleaner, and I’d enjoy writing components this way, but in my opinion, the thing that makes me love destiny is how native it is, everything nowadays are just polyfills and ‘fake native implementations’, a component not being a class and not being able to extend a html element does quite the opposite, it removed the native aspect of it and possibly feels like ‘magic’

I’m torn, but would be curious to hear you thoughts on the above

[0kku]

@0kku coming from a react background, this approach seems nice and I guess it feels cleaner, and I’d enjoy writing components this way, but in my opinion, the thing that makes me love destiny is how native it is, everything nowadays are just polyfills and ‘fake native implementations’, a component not being a class and not being able to extend a html element does quite the opposite, it removed the native aspect of it and possibly feels like ‘magic’

I’m torn, but would be curious to hear you thoughts on the above

Just to be clear: the component would still extend HTMLElement after instantiation, but wouldn't be doing so until after the component has been passed to the template. The intention of the idea was for it to convert the function into a class that extends HTMLElement under the hood. However, I do see your concerns regardless. Also, this conversion would be a non-zero amount of work, so technically it would have slightly more overhead as well.

[0kku]

By the way, something like this would already work for things that don't require lifecycle hooks, since all these things are nothing but JS values:

import { html } from "destiny";

function myTemplate (defaultName: string) {
  const who = reactive(defaultName);

  return html`
    <label>What's your name? <input type="text" value=${who} /></label>
    <p>
      Hello, ${who}!
    </p>
  `;
}

function anotherTemplate () {
  return html`
    <h1>Demo</h1>
    ${myTemplate("visitor")}
  `;
}

document.body.append(anotherTemplate().content);

[ebebbington]

Yeah fair enough, I do see the functional components being nicer in every way, plus I guess it means you pass in values (like above) as opposed to using custom attributes

I’m warming towards functional components now :) imo

[0kku]

Closed as infeasible and too magical (the bad kind).