Tweet

Steve Polito

Apr 5 • 3 tweets • 2 min read

I'm exploring how to send secure messages in #rails with ActiveSupport::MessageVerifier.

What makes the message secure?

🔐 It's not stored in the database
🔗 The URL expires, cannot be tampered with, and is non-sequential.

Code snippets in 🧵

Using ActiveModel gives us a nice API to work with, without needing to save the record to the database.

We can then convert an instance of that model into a secure message generated with ActiveSupport::MessageVerifier.

• • •

Missing some Tweet in this thread? You can try to force a refresh

This Thread may be Removed Anytime!

Twitter may remove this content at anytime! Save it as PDF for later use!

More from @stevepolitodsgn

Steve Polito

@stevepolitodsgn

Mar 14

Have you ever needed to get the most recent record for each user in #rails, but didn't know how to do it without using map?

Here's one way to do it with Active Record 👇

Calling group(:user_id).minimum(:id) returns a hash where the key is the user_id and the value is the ID of their latest (or first) post. Calling .values simply returns the IDs.

We can then pass that list to where(id:) to return a list of the latest (or first) posts per user.

Since the IDs are set in sequential order, the minimum ID is the ID of the user's first post, and the maximum ID is the ID of the user's latest post.

Read 5 tweets

Share this page!

Steve Polito

People who liked this thread also liked...

Try unrolling a thread yourself!

More from @stevepolitodsgn

Steve Polito

Did Thread Reader help you today?

Don't want to be a Premium member but still want to support us?

Like this author's thread?