Renderers: consider wrapping one source of truth?

There are already multiple issues and PRs open with people trying to contribute various attempts at Vue, react, etc.

Meanwhile, the repo already has angular and lit renderers.

If you start accepting these contributions, you'll basically end up with a component catalog ported to each known framework over time.

This seems like a pain to maintain since they're all going to provide the same functionality but through duplicated code tailored for each framework.

Have you considered just wrapping one source of truth in thin components for each of the frameworks?

Under the hood, this is the same as any other component catalog. You could store your source components as custom elements (lit), but provide react/vue/etc wrappers which render those CEs.

This way you maintain one copy of the component logic and various thin wrappers for sake of giving better DX to those using other rendering libraries.

Look at the existing angular and lit renderers in the codebase to understand the current architecture. The issue suggests creating a single source of truth, likely as custom elements, and then providing thin wrappers for other frameworks. Investigate how component logic is currently duplicated and explore patterns for creating framework-agnostic core components and their respective wrappers.

索引モデルが issue の本文から書いたものです。