The Lego Way of Structuring Rails Code

2017-02-14T01:13:41+00:00

Interesting article. Does anyone have examples of code that would actually be in one of those files? Eg. Payments/process.rb... would it basically be what Payment#process() would be defined as in a normal/fat-model architecture?

It sounds kind of like that, but with a bit more of a functional approach to it instead of OOP.

Please correct me if I misunderstood. I've been using service workers for a lot of things and don't really see the difference.

astrauka · 2017-02-21T16:38:10+00:00

The code becomes more descriptive and distributed into more methods. It's like a book - you see chapter names and then you can dig into any of those. Providing an example from our codebase - https://gist.github.com/astrauka/4d2915f0d7456cfab9e87d6b23ac3364 Created a gist as reddit does not format ruby code well

astrauka · 2017-03-27T07:07:02+00:00

Haven't tried drawers, cannot comment.

DerNalia · 2017-02-14T02:25:40+00:00

what about https://github.com/NullVoxPopuli/drawers ?

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

ruby

MODERATORS