Hexagonal Architecture Guidelines For Rails

Re:Hexagonal Architecture Guidelines For Rails by nimblegorilla on Tuesday March 18, 2014 @11:46AM (#7422599)

I agree, but I see "one line per controller action" as a guideline that doesn't need to be followed religiously. Almost every rails app that I come across has too much domain logic in the controllers. I'm refactoring an ecommerce app where the developers put 400 lines of payment processing code inside one controller.

Things like authorization should be mostly contained in the root controller and not sprinkled around your controller actions.

What kind of decorators are appropriate to apply to models from a controller action? I'm sure there are valid scenarios, but most of that should also go somewhere else.

[ Parent | on HN ]

Re:Hexagonal Architecture Guidelines For Rails by ryanbrunner on Tuesday March 18, 2014 @01:34PM (#7423475)

If you had a view decorator that applied presentational logic to a model, I don't see a problem at all in including that in a controller. I wouldn't have any issue at all with a controller action that looked like:

    def index
      respond_with PersonListDecorator.wrap(Person.all)
    end

[ Parent | on HN ]

Re:Hexagonal Architecture Guidelines For Rails by nimblegorilla on Tuesday March 18, 2014 @05:33PM (#7425148)

Yeah I think that is a good idea. But to be fair: your example is only 1 line and has no business logic.

[ Parent | on HN ]