next_rails_scaffold 0.1.11 → 0.1.12

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f03d199ec6a029410c9c0626e7eaa604e8e454c772b161a5ef884e5503d4e284
-  data.tar.gz: c0c56ac0d95b65e3979c0120f59db0f494a980fdcd8f4138c037b74ce43aff5c
+  metadata.gz: f62c69ac348b5a9eb16f7bf25be74b6ceb753d0a7fdcb023c0e20fa03ae05fec
+  data.tar.gz: 9f0fe1e479a70c791e20ddba38db1396c90329b64d9b0bbb942078bf1d063306
 SHA512:
-  metadata.gz: 8b3369a429e58f2739888d89ef20fa368124b27e5cfcd302eaedc9d09173391ef42a46ce3d99be58320a3fb22782e92545182b3ff19e160c162f3aed34d3750c
-  data.tar.gz: 87dcb6bc580cc1a9aa8afd0aa0314ff037ae0d7f31cad7a35a653862f46ea3f4c472f84a6faabc8c2780d95e7bf7905e8cbe03811345f414492eef05b514bd1e
+  metadata.gz: b174d2f71fcc7d0c25013c222b8f5127252a399da45d2f3d59b7c27323b11e724049ac0f5789bf8b9302fca3fddd9083216661cb04407c170ebd8503a6e67908
+  data.tar.gz: fd369e1888cefdb74e5246bff429ffc87843130268aa951530fc2bd8dc91bbc125134c20b282a9e1cfa17d81dba340cd928315c24542cbc307bba6f0be4c9f1e

data/README.md

@@ -15,6 +15,14 @@ Currently, https://www.hygen.io/ is used to create Next.js code, and the https:/
   </a>
 </div>
 
+## Why?
+
+In one of my posts on [Medium](https://medium.com/@raphox/rails-and-next-js-the-perfect-combination-for-modern-web-development-part-2-308d2f41a767) I go into more detail about the reasons why I created this project. But to summarize, I'll list a few relevant points:
+
+1. When I compare the alternatives offered by [Hotwire](https://hotwired.dev/) with the entire React ecosystem, for me Hotwire is stuck in the way of developing web applications that were practiced more than ten years ago when there were no frameworks like React;
+2. The maturity and ease of the Ruby language and the Ruby on Rails framework justify having more than one language in the same project;
+3. Nothing prevents me from keeping the static site or Single-Page Application (SPA) for smaller projects and, if there's a need or demand, later maintaining my API and configuring my Next application to run on a Node server and offer SSR;
+
 ## Key Features:
 
 - **Automatic Frontend Setup:** The gem automates the creation of a frontend directory within the Rails project, ready for Next.js development.

data/lib/next_rails_scaffold/engine.rb

@@ -3,6 +3,5 @@
 module NextRailsScaffold
   class Engine < ::Rails::Engine
     isolate_namespace NextRailsScaffold
-    config.eager_load_namespaces << NextRailsScaffold
   end
 end

data/lib/next_rails_scaffold/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module NextRailsScaffold
-  VERSION = "0.1.11"
+  VERSION = "0.1.12"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: next_rails_scaffold
 version: !ruby/object:Gem::Version
-  version: 0.1.11
+  version: 0.1.12
 platform: ruby
 authors:
 - Raphael Araújo
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-11-25 00:00:00.000000000 Z
+date: 2023-11-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails