lokaler.lnu.no VS view_component

However, it adds a lot of overhead if you mainly use dynamic pages, and not highly interactive ones. Therefore in my latest project we are trying to use Stimulus and Turbo for everything, to see how far that can stretch before we wish we had reached for a tool like React. So far we haven't needed React for a single thing, and we're building a fairly complex app (dynamic maps, filters, search, and inline editing).

When searching for examples of table components built with the ViewComponent gem, I was surprised to find none. After some inquiries, I came across examples that worked like this:

View components offer two primary ways to interact with the component: passing arguments to the initializer and using slots:

For example, splitting out views into partials? Or the new ViewComponent feature that's becoming quite popular - https://viewcomponent.org/

I used to do "pure ruby" approach to that -- but basically wound up realizing I was re-inventing github's view_component. Their design goals were similar enough to what I was trying to do, that it made more sense just to use that, rather than try to re-invent it myself.

ViewComponent

The linked one is my Rails implementation, written for ViewComponent. The official version uses Nunjucks.