@MrSimonBennett@kompakd Hell I would pay well over 40k pounds for a solid php/laravel engineer right now. Can’t find engineers to save our lives in the states.
@mateusjatenee@michaeldyrynda@inxilpro Yeah I should have been more specific - I know Eloquent uses magic methods and doesn't have public properties. But I did some looking around and it seems that what I stated previously is the direction the preferred convention is headed.
@michaeldyrynda@inxilpro Looks like I may have missed the boat on this one. It looks like the new convention is completely ditching getters/setters in exchange for public typed properties?
@GrahamJCampbell@michaeldyrynda@dr4goonis I tend to agree with you on this one. Although traditionally I've always used snake case for my variables up until recently. Working on a legacy-ish project that is all camel case. I still can't decide how I feel about it.
@GrahamJCampbell@michaeldyrynda@dr4goonis I thought that PS12 still allowed for choice between camel case or snake case with variable naming, is it straight camel case?
@michaeldyrynda@inxilpro It's certainly not just for IDE behavior, it's just helpful in that regard. I definitely don't agree that it's anti-convention and needless abstraction, in fact your everyday purist wouldn't have it any other way. At the end of the day it's personal preference.