rails-7-fullstack VS view_component

**NextJs is just a choice, not a requirement **The API made using Ruby on Rails is completely independent of the Next JS client application developed with NextJs. You could use any RESTfull client application to consume the existing API. In my project, I am using the NextJs project as a subfolder of my Rails repository, but you could put it anywhere.

You could see the resulting code at https://github.com/raphox/rails-7-fullstack.

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.