How to use ActiveRecord callbacks in very complicate case?

Question

It become a nightmare when we have a complicate logic in ActiveRecord model. Now we are maintaining a complicate rails project. As one of the most complex models, we have more than 4000 lines code and more than 140 callbacks. It is depressed when new features comes in. No one can tell which part is impacted and need to update.

Does anyone has suggestion for the case? Any better idea to organize the callbacks? Or we need to avoid to abuse using callbacks, and any other solution need involved?

score 0 · Answer 1 · edited May 23 '17 at 12:27

0

You need think using the DCI pattern. Is do to your case. You can have some information about that in this SO questions : DCI - Data, Context and Interaction - Successor to MVC?

edited May 23 '17 at 12:27

Community

1
1

answered Mar 14 '12 at 15:39

shingara

46,608
11
99
105

We have think about it. Any gems working on it? Or do you have any samples on that? – liangyan.cn Mar 15 '12 at 05:13
I add a link to an SO question speaking about that. – shingara Mar 15 '12 at 08:52

score 0 · Answer 2 · answered Mar 14 '12 at 16:49

0

You could move some callbacks to Observers . This can make your model lighter.

answered Mar 14 '12 at 16:49

santuxus

3,662
1
29
35

I think we are over used callbacks. If i change callbacks into Observer. It will be over used observer. The problem is still there. – liangyan.cn Mar 15 '12 at 05:15

How to use ActiveRecord callbacks in very complicate case?

2 Answers2