Andy Duong

> @andyduong1920 got it. But we also not have the `data_migrations` in the template, correct? 🤔 I have opened a PR for the `data_migrations` part here FYI @rosle https://github.com/nimblehq/elixir-templates/pull/148

@malparty any update on this issue

In case we merged the https://github.com/nimblehq/rails-templates/pull/419 which use the new Figaro fork version, not sure we would need to remove the Figaro gem or not ;)

@malparty yeah, we can remove the Figaro way @malparty 👍

Hi @malparty, as you changed from Pagy to `Kaminari` in one of your projects, and you're using Kaminari now, do you think this feature is needed?

Please hold on this issue as we are having some issues on the `View helper` with Kaminari on Ruby 3.2 and Ruby 3.1 :D and I just realized the last...

The issue we faced in our project is different, it's because we used the older Kaminari version :D upgraded to 1.2.2 and everything works as expected, so no issue with...

Same issue too ``` Erlang/OTP 23 [erts-11.0.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [hipe] [dtrace] Interactive Elixir (1.10.4) - press Ctrl+C to exit (type h() ENTER for help) iex(1)> require ExVCR.IEx...