Re: Design question: Is it really a good idea for models having “side effects”?

On Fri, Feb 20, 2015 at 4:23 PM, Gergely Polonkai wrote: > Hello, > > I’m currently implementing a finite state machine in my application using > Django FSM[1]. In the Usage section of the README the author said that > “This function may contain side-effects, like updating

Re: Design question: Is it really a good idea for models having “side effects”?

I'm not sure if there's an official stance on that, but I believe that since Django is a "MVT" framework, that kind of logic does not seem to be appropiate neither for templates nor views, so models seem like the logical choice. That way you can also make sure that the side-effect that you want

Design question: Is it really a good idea for models having “side effects”?

Hello, I’m currently implementing a finite state machine in my application using Django FSM[1]. In the Usage section of the README the author said that “This function may contain side-effects, like updating caches, notifying users, etc.” Opposing this statement, the Symfony PHP framework’s