Pagy VS phlex

Now, let's dive into the pagination part of this post: setting up Pagy for handling pagination in our Rails application. If you haven't included the Pagy gem in your project, you'll need to add it manually. Here's how you can do it:

Several gems are available for pagination in Rails, but the Pagy gem is one of the most popular and efficient. It is a fast and lightweight library that provides a simple and flexible API. In this article, we’ll explore how to use it to implement pagination in Rails.

> Am I understanding correctly that there’s a significant difference in performance between using a ViewComponent + a partial vs. a ViewComponent which renders html via a tag - from inside the component?

I don't think there will be much difference at all in everyday use, but some libraries that value performance don't avoid templates for that reason, Pagy for example.

https://github.com/ddnexus/pagy

Personally I omit them in my projects whenever we want to customise attributes, I hate seeing stuff like this in templates:

    
Some header

The next step was about backporting the templates, adding Pagy gem for handling pagination and creating the controller. I was then able to show the listings with the models, but the filtering was not working.

On the backend, we'll need a few tools. Apart from the classics (ActiveRecord scopes and the pg_search gem), you’ll see how the (yet officially unreleased but production-tested) all_futures gem, built by SR authors, will act as an ideal ephemeral object to temporarily store our filter params and host our search logic. Finally, we’ll use pagy for pagination duties.

Pagination

In our application, we will use Pagy to implement pagination. Let’s install Pagy now, following along with the Pagy quick start guide.

For pagination I tend not to use gems like pagy or kaminari, instead implement this functionality just using limit and offset.

Kaminari hooks onto ActiveRecord associations and makes it super easy to page them. Pagy is another option that seems to have a solid API but I haven't tried it yet.

But how is this implemented? Well, if you use pagination in your index methods with gems like pagy, kaminari or will_paginate you will find that the same idea is happening here, they are using the power of SQL's LIMIT and OFFSET to fetch only a portion of the data each time. So in the 1 million users example, find_each will perform 1000 thousand queries with a limit of 1000 while changing the offset properly so we don't miss any record.

The community was a delight! I can't even count how many people I connected with, and it was just great to meet people whom I had previously only interacted with online. Also got to meet a lot of those people who significantly contribute to the Rails ecosystem. Everyone I said hi to was more than willing to spare time and nerd out and share experiences. I was also thrilled to connect with Philip, who shares my enthusiasm for Phlex. He provided me with some exciting ideas for creating an even more crazy yet cohesive form object with Phlex.

Why use ActiveAdmin or RailsAdmin: Brick is not nearly as configurable -- at least yet! With Brick you can drop in your own model / controller / view template and it will use it, but on its own you can not change theming / use it to do templating tricks / etc. Currently working hard to arrive upon a straightforward and logical approach so that all of this will be possible. Looking into Arbre (used by ActiveAdmin) and Phlex for inspiration.

Phlex is an incredibly refreshing gem created by Joel Drapper. It introduces a remarkable way to build views in pure Ruby, as exemplified below:

A few months ago I came across https://www.phlex.fun and thought it was a nifty little library that could be useful for creating components. Since then I've been playing around with it in Rails, using it more seriously, and finally took it to a point where I built a Rails application with 100% Phlex components and 0% Erb. The other crazy thing is I figured out how to inline the Phlex view components into a controller, so prototyping Rails apps feels vaguely familiar to prototyping one in Sinatra.

A colleague has been using Phlex and I’ve since tried it as well. For me having it all be straight ruby, in one file, has worked and just from my personal preference something I’ve enjoyed over view_components.

phlex

You might want to take a look at Phlex, which essentially has the same syntax: https://github.com/joeldrapper/phlex