Rails Erd VS Pagy

I've been using a simpler version of this https://github.com/voormedia/rails-erd but it seems neat that this comes with a web app and a query language.

Graphviz

Use the rails-erd gem to generate an ERD: http://voormedia.github.io/rails-erd/

Entity Relationship Diagrams (ERDs) are super useful for visualizing databases. For an ERD example, or to see how to make one, see this gem. Though note that gem is only for rails 3-5.

You should take a look at rails-erd, it is really easy to set up and works quite well

At my work we've got a 10-year-old Rails app (originally started as Rails 3), rake stats says we're now over 100kloc (non-test). We've got a huge amount of complexity and cross-dependencies (not to mention, probably-dead code), and the majority of our test suite runtime (about 40h non-parallelized) is in cucumber because developers can't get a clear view of the level of the app they're dealing with, and I suppose don't feel they can trust the lower layers of the application. Running rails-erd on it generates the very definition of spaghetti, it's gross.

This PR fix the build

Pagy released version 43 this week. It's advertised as a complete rewrite of its internals and APIs.

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.