Ron Lobo
Ron Lobo
Personally, please no getter/setter stuff, for various reasons: https://www.yegor256.com/2014/09/16/getters-and-setters-are-evil.html https://blog.sentry.io/2018/04/05/you-cant-rust-that https://marcus-biel.com/getters-and-setters-are-evil/ https://dev.to/scottshipp/avoid-getters-and-setters-whenever-possible-c8m https://www.infoworld.com/article/2073723/why-getter-and-setter-methods-are-evil.html
Eventually, something is used if it is there, especially when more than one dev or an engineering team works on the same project. Invariants can also be captured in the...
I agree, however, personally I call getters accessors. Mutators (setters) are fine as long as they return a newly allocated data structure instead of modifying the existing one. This paradigm,...
Just want to throw in: http://www.ange-agostini.com/blog/non-classe/laravel-ignore-current-record-when-using-unique-rule-with-ardent.html As a quick fix in your update method modify the rules of your model, e.g.: $project = Project::find($id); Project::$rules['name'] = Project::$rules['name'] . ',' ....
Thanks for this tip, will try it :)
:+1:
Any news on this? :8ball: