From eef2a250a7dfdf1c6d3a1781594642126d86e849 Mon Sep 17 00:00:00 2001 From: Meg Gutshall Date: Sun, 30 Jul 2023 15:25:38 -0400 Subject: [PATCH] [skip ci] Update blog post link (#1425) Update link for "Why you Ruby class macros (might) suck (mine did)" blog post Co-authored-by: Meghan Gutshall --- docs/docs/going-further/other-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/going-further/other-notes.md b/docs/docs/going-further/other-notes.md index bf8ea417..68785bcb 100644 --- a/docs/docs/going-further/other-notes.md +++ b/docs/docs/going-further/other-notes.md @@ -182,7 +182,7 @@ for an `auth_object` key in the options hash which can be used by your own overridden methods. Here is an example that puts all this together, adapted from -[this blog post by Ernie Miller](http://erniemiller.org/2012/05/11/why-your-ruby-class-macros-might-suck-mine-did/). +[this blog post by Ernie Miller](https://ernie.io/2012/05/11/why-your-ruby-class-macros-might-suck-mine-did/). In an `Article` model, add the following `ransackable_attributes` class method (preferably private):