Facade design pattern in Ruby on Rails
Krzysztof Kempiński
2907

Law of demeter is the minor issue here

I agree with:

“I mean, your goal shouldn’t be to use only one facade by moving every initialisation from the controller to a new class.”

_____________________

index method “replaced” with “IndexObject” :/

Why to try “the oneliner” with such different data scopes and meaning

Wouldn’t be enough polishment with @users_lists object providing properly decorated users:

@users_lists.active_users

@users_lists.vip_users

Mixing User “lists” with “current_user“ ”and “User.new” in one object

breaks hard single responsibility principal

but … you mention that above ;) +1

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.