Handling modal forms with Rails, Tailwind CSS, and Hotwire15 Jul 2021
September 2022 update: Since this article was written, Rails 7 and Turbo 7.2 have been released. There are new, simpler techniques to building modal forms with Turbo now. I published an updated version of this article after the release of Turbo 7.2, I recommend reading that article instead.
The release of the Hotwire package of Stimulus and Turbo has brought a tremendously powerful set of tools to Rails developers who want to bring the speed of a single page application to their users without sacrificing the development speed and happiness that Rails is known for.
Today we are using Hotwire, Rails, and Tailwind CSS to build a modal form submission flow.
With just a little bit of Stimulus and Turbo, we will create a user experience that opens a modal on click, retrieves modal content remotely, and cleanly handles successful form submission and form errors.
This modal flow will help us learn a few of the core concepts of Hotwire while demonstrating how to implement a very common user experience in modern web development.
The finished product will look something like this:
I am writing this guide assuming that you are comfortable with Ruby on Rails and that you have some level of familiarity with Stimulus. You do not need to be an expert on either.
While we use Tailwind CSS to make our modal implementation simple, you do not need experience with Tailwind. If you prefer, you can implement your own, non-Tailwind modal and still get value from this guide.
You can find the complete code for this project on Github.
Let’s get started.
We are going to start with a fresh Rails 6.1 application. If you prefer, you can follow along in an existing Rails 6 application, just be sure you’ve got Hotwire and Tailwind 2 installed.
If you want to skip the setup steps and don’t have a repo handy, clone down this repository, bundle install, and you’re good to go. If you take this route, jump ahead to the setting up comments section below.
To start from scratch, first open your terminal and run these commands:
Next, we will setup Tailwind CSS.
In your terminal, run:
Then update postcss.config.js:
And update tailwind.config.js:
Next we’ll import Tailwind into the application. In your terminal run:
And update the newly created application.scss file to import tailwind:
Next, update your existing
application.js file to import application.scss:
That’s a lot of copy and pasting, hang in there. One more to go before we get to the fun stuff.
app/views/layouts/application.html.erb with the below:
Perfect. Next we will scaffold up a
Comment resource, which we’ll use to build our modal form submission flow.
Setting up comments
First, generate a Comment resource. In your terminal:
Then update the comments index view with a simple list view layout:
The index view loops through the comments and renders the
_comment partial for each one. Let’s fill that in with the below:
At this point, boot up your Rails server and head to http://localhost:3000/comments. You should see a layout that looks something like this.
Go ahead and create a few comments to test things out.
Once you confirm everything looks right, head on to the next section where we will add a modal to the replace the standalone New view that the scaffold generator provided.
Add Tailwind Stimulus Components
Rather than reinventing the wheel and writing a Stimulus controller to open and close our modal, we’re going to use Tailwind CSS Stimulus Components. This project provides easy-to-use, production-ready components for a variety of common front-end user interactions built with Stimulus and Tailwind, including a ready-to-use modal component.
One of the joys of Ruby on Rails development is the incredibly robust ecosystem of community-built libraries that help reduce the effort that goes in to building Rails applications.
While the Stimulus community is still growing, projects like Tailwind Stimulus Components are already making it easier to build Stimulus-powered frontend experiences.
First add tailwind-stimulus-components to your application. From your terminal:
While we are going to use the basic behavior of the Modal component, for our purposes we’ll need to add a little bit of extra functionality to the modal controller. We can do this by extending the Modal controller.
First, in your terminal:
Then update the newly created controller as shown below:
Wire up the modal
ExtendedModal controller created, we are ready to start building our Hotwire-powered modal interface.
First, create a partial to hold the modal content. From your terminal:
And fill that partial in with the below:
This partial contains the body of the modal.
The style is mostly copied from the tailwind-stimulus-components documentation, the most important parts for our project are setting the data-extended-modal-target, which is required for the modal to open and the empty
<form id="comment_form"> tag. This empty tag serves as a placeholder for the comments form content that will be populated when the modal opens.
Next up, we’ll update the comments index view to connect our modal controller to the DOM:
Now we are into the meat of the project. Let’s walk through what we changed here.
First, we render an empty
<turbo_frame>. We’ll populate this frame with the content of the modal when the New Comment link is clicked.
Next, we connect our controller to the dom with
data-controller="extended-modal" and override the default behavior of the modal controller with
prevent-default-action-opening="false" which tells our modal controller to allow the link_to action to run as normal.
The New Comment
link_to which has two data attributes. The first is a standard Stimulus action attribute which fires the open function of our modal controller on click.
The second is a Turbo attribute which tells Turbo to render the response from the server in the comment_modal
<turbo_frame> that we added at the top of the view. Without this data attribute, Turbo would not know where to place the response from comments/new and clicking on the New Comment link would just render an empty modal.
The basic flow of our modal is this:
- User clicks on New Comment link
- The click fires the extended-modal#open function which opens the modal
- Because we told the open function to allow the default action to be followed, a request is sent to comments/new
- When a response is received from comments/new, Turbo steps in and attempts to insert the response into the comment_modal turbo frame
Finally, we replace our comments wrapper div with a “comments” turbo_frame_tag. We will use this frame later to insert new comments after a successful form submission.
Fancy stuff, but we’re not quite there yet.
Next we need to update the new comments view and the comment form partial in order for the modal to properly render the comment form after it opens.
Let’s start with updating the new view:
Here we’re rendering a comment_modal turbo_frame tag and inside of that rendering a turbo-stream that looks for an element with an id of comment_form and replaces it.
Next, the form partial:
The form is almost entirely standard Rails form_with content. The important bits are passed in to the
form_with. First we set the id of the form to comment_form. Recall that the turbo-stream in comments/new is looking for an element with that id.
Next, we add a data-extended-modal-target attribute of “form”. We will use this target attribute later to reset the form after a successful submission.
With those views in place, let’s update the comments controller to send turbo_stream responses when the posts#create action is called:
Here’s where the turbo_stream magic happens.
When our comment form is submitted, the create action is called and, if the comment saves, the server sends a turbo_stream response that appends the comment partial to a comments turbo_frame. Note that we do not need a comments.turbo_stream.erb partial, the existing html comments partial we have gets used automatically.
The final step to properly handling our form submission is to close the modal after the form is submitted successfully. To do this, we will add a small function to the modal Stimulus controller and then attach an event listener to the DOM.
First, add this function to
handleSuccess simply checks a boolean success value and, if success is true, we close the modal and reset the form. If success is false (meaning the form submission failed), our Stimulus controller does nothing.
Finally, to ensure handleSuccess is called after the form is submitted, update the modal partial as shown:
Here we’ve added a data-action attribute listening for the
turbo:submit-end event. When that event fires, our modal controller’s handleSuccess function is called, allowing our modal to close when the form is submitted successfully.
Whew. At this point, if you’ve been following along with each step, you should be able to load up the comments index page, click the New Comment link, type in a comment and submit it successfully. If everything is working, the new comment link will open a modal, and submitting the modal’s form will close the modal and append the new comment onto the comment list.
Handling form errors
To wrap up, we’ll update our CommentsController to handle errors. This’ll be quick.
First, update the comments model to validate that body is present so that it is possible to have an invalid comment submission.
Then head to the CommentsController and update the create method as shown:
In the else block, we’re again rendering a turbo_stream response. This time, we target the comment_form turbo_frame and replace the content of frame instead of appending. We also send along a 422 status code so that the turbo:submit-end properly sets success to false. Otherwise, the default status code of 200 would cause our modal to close.
With this error handling in place, submitting the modal form without typing anything into the body field will cause the form to rerender with the errors listed above the form, like this:
As our very last step, thanks to Turbo’s caching, an edge-case UI error can happen now that we have error handling in place.
If a user attempts to submit the form with a blank body, and then corrects their error and successfully submits the form, clicking the New Comment link again will open the form with the error section still present on the modal.
We can clear that up with a small addition to our modal Stimulus controller:
Here the clearErrors function looks for the presence of errors on the form and removes them from the DOM if they exist. To make this work, update the form partial to add the data-extended-modal-target onto the errors container:
That’s all for today. I hope that this guide has helped you see some of the power you can unlock by adding Hotwire to your Rails stack.
With Hotwire, we were able to build a modal-based form submission flow that eliminates full page turns and delivers a modern-feeling, performant solution while still keeping our code easy to follow and build upon for any Rails developer.
Hotwire is still new, and still evolving rapidly, in the future we can expect even more powerful functionality and even tighter integration with Rails as the community continues to add Hotwire to new and existing Rails applications.
Here are a few resources I used as I wrote this guide:
- Tailwind Stimulus Components: In addition to modals, this project gives you ready-to-use Alerts, Dropdowns, and Tabs, among other things. Before you roll your own component, check here.
- How to use modals with forms in Rails using Turbo: This article served as a great starting point for my work and helped me reach the solution that I presented. Highly recommended if you’re interested in another approach to handling modal forms with Turbo
- The Turbo and Stimulus handbooks
- The Turbo source code: Turbo is evolving rapidly enough that even the official documentation can sometimes lag behind. Reading through the source can be a great way to learn more about the options you have for solving a problem, and for understanding what’s going on behind the scenes.
Thanks for reading!
About the author:
I’m David - a solo founder and consultant. I write about software engineering, Ruby on Rails and the Rails-y ecosystem, product management, and the lessons I learn as I work to build sustainable SaaS businesses.
My current project is Vestimonials, an async video communication tool to help companies collect and share video testimonials from their employees and customers.
I’m available for Rails, product management, and strategy consulting. Get in touch if you have questions about this article or anything else that’s on your mind.