TIL about helpful flags built-in to the rails routes task.

-g

allows you to grep the output and filter for any routes that partially match the URL helper method name, the HTTP verb, or the URL path.

---

Example: rails routes -g new_comment</br> rails routes -g POST</br> rails routes -g admin

-c

allows you to filter output by controller name.

---

Example: rails routes -c users</br> rails routes -c admin/users</br> rails routes -c Posts</br> rails routes -c Devise::Sessions

--expanded

makes the output easier to view in smaller terminals.

---

Example: rails routes --expanded</br>

--unused

lists routes that are "unused" in your application. An "unused" route in Rails is a route that is defined in the config/routes.rb file but is not referenced by any controller action or view in your application

---

Example: rails routes --unused

Rails guide source

WSL Woes

Whenever you copy/paste files from Windows to the Linux subsystem I always get these weird Zone Identifier files that I don’t want!

You can remove them all with this command:

find . -name "*:Zone.Identifier" -type f -delete

Configuring Solid Cable on Render

Rails 8 added a lot of new features. Solid Cable comes as a drop in replacement to Action Cable and, by default, it uses the database instead of requiring Redis.

I generated a new app (with Postgres), added some tables and turbo streams and then deployed to Render. The deployment failed!

Exited with status 1 while building your code.

This error message wasn’t very clear! But the line of code pointed to a broadcasts_to in my Comment model, so I was pretty sure it was Solid Cable related.

after_create_commit -> { broadcast_before_to "...", target: "...", partial: "..." }

I learned that Solid Cable runs in a separate database, which I assume Render didn’t like. I followed the instructions in the Solid Cable README to configure Solid Cable to work with a single database and I was able to deploy to Render!

1. Copy the contents of db/cable_schema.rb into a normal migration and delete db/cable_schema.rb
2. Remove connects_to from config/cable.yml
3. bin/rails db:migrate

🎉

Markdown footnotes

I forget this all the time.

just do this:

Some text[^1].

Some other text[^2].

The identifier in the square brackets does not have to be numeric[^my_footnote].

[^1]: Some footnote.
[^2]: Other footnote.

[^my_footnote]: This also works fine.

This is not supported in GitHub repository code.

Naming DB indexes

Rails 7 apps have a limit on autogenerated index names of 63 characters.

ArgumentError: Index name
'index_codeblock_submission_on_user_id_and_lesson_id_and_block_id_and_internal_submission_id' on table
'codeblock_submission' is too long; the limit is 63 characters.

To work around this you can choose a name to use instead of the autogenerated one.

update the migration with the name key and value:

    add_index :codeblock_submissions, [:user_id, :lesson_id, :block_id, :internal_submission_id], unique: true, name: "index_codeblock_submissions_on_block_lesson_user_submission"
  end

Source