About the Book
The default structure of Rails applications hasn't changed all that much in over a decade. And with good reason: this directory structure makes it easy to jump into building a Rails application.
While I agree that this way is still extremely simple and great for getting started within a Rails application, I do not agree that this is the best way to organise a Rails application in 2018 with long-term maintenance in mind. A decade of Ruby development has produced some great alternatives to Rails' MVC directory structure that are definitely worthwhile to consider.
The `rom-rb` gems allow us to interact with a database with just as much ease as Active Record, but with the added benefit that persistence and business logic aren't bundled together in the same class.
The `dry-rb` gems allow for splitting the validation logic away from the business logic's class (dry-validation) and also provides a sensible alternative to the community-wide pattern of service objects (dry-transaction).
This book covers how you would go about integrating these gems into a brand new Rails application, building features in an iterative fashion, resulting in a maintainable structure for the whole application.
- Who is this book for?
- Where Rails falls down
- Messy controllers
- The problems with Active Record Models
- We can do better
Getting started with ROM and Dry
- Application setup
- Boot Configuration
- Specifying the container automatically
Rails, meet ROM
- Generating our first ROM-powered relation, migration, repository and model
- Connecting a Rails controller with ROM
- Showing a particular project
Validating projects during creation
- A small interlude about that contributors method
- Creating a validator
Let’s talk about service objects
- Building our first operation class
- Integrating the Projects::Create class with the controller
- Refactoring the operation class one step further
Working with associations
- Creating a tickets repository, relation, model and migration
- Creating all the parts for users
- The contributors method
Two kinds of views
- Displaying contributors
- Finish the CRUD actions for the ProjectsController
- Add a TicketsController
- Add Devise to the application
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $12 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.