Rails: validation that spans multiple models, where to put it?
"YOU AND THE ART OF ONLINE DATING" is the only product on the market that will take you step-by-step through the process of online dating, provide you with the resources to help ensure success. Get it now!
Create a module in your lib directory and then include it in. You can also create a parent class from which your models inherit and put it there, but that seems a bit over the top for something that simple.
In rails the best practise is to have fat models and thin controllers. Now I have a situation where I am interacting (updating mostly) 3-4 model records. Where should I put this logic?
Should I make a 'service' type class and put it in lib?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
How to improve the performance of this query that spans across multiple databases?
Rails 2.3.8: Callback that will happen before save and validation (even when there's no validation)?
Different validation on multiple models in a view?
MVC 3 Make a change to an input id and still have the validation work? Multiple identical models in one view?
Custom validation with multiple models?
Rails - Skip rails validation for subclass?