2 ms·
Ah, it's a design element. I actually remember looking at that area and noticing the stitching and that the border looked nice, but to be honest my brain only s
by rhizome 16y ago
Ah, it's a design element. I actually remember looking at that area and noticing the stitching and that the border looked nice, but to be honest my brain only saw a Levi's tag hanging there (it didn't look like a date). Also, there is no year. Anyway, mea culpa, I'll look harder next time.
Sure, it's 81 lines shorter, but I don't know what's going on there, either. Its one thing to express a method in an elegant fashion, but an entirely different thing to hide it off someplace, which is how I read what is happening here. I'm guessing there are some instance variables available afterwards? Plus, it's an additional dependency.
And yeah, I read the title "Why You Shouldn't Use Rails' Scaffolded Controllers" and "...the state of the art has moved on" to mean that what you were talking about was supposed to be better.
- r00k 16y agoYeah, fair enough, the date is a bit easy to miss. Not my favorite aspect of the theme I'm using. Sure, it's 81 lines shorter, but I don't know what's going on there, either. Sure, but I'd imagine most developers have the default controller actions memorized by now (I do). So, this class you're inheriting from does exactly what you're used to. Only now, you don't have repeated controller code and functional tests everywhere. Really, this is an application of the DRY principle to app/controllers.