Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@CrunchyNut yeah... That's most likely shit.
Maybe take a look at GIT History... Highly guess everything was public before (or even worse: __set/__get).
SQL part... Searches can be very tricky. Depending on what it does, it might not be doable in an ORM or with a high performance penalty. Depends largely on the ORM.
And yes.... The legacy shit sucks.
If you'll rework it, maybe think about DTOs and seperation of the SQL part from data validation / preperation...
But still, classes like that are mostly looking like someone puked after an all u can eat international buffet
This is how I feel after working, almost exclusively, with PHP over the last 4 years.
When you don’t hit all the job description check boxes
“Just a quick fix” Classic start to a reported ticket. Ticket states that a form field was not doing anything.
Think to myself ok this sounds like a nice easy one for the morning. A few hours later I find something like the following written by a senior member of the dev team.
SearchClass {
//...list of getter and setters
Private $snakeCaseName;
SearchFunction() {
Foreach($this as $property => $value){
//... if property keys = string for each object property then do code
If($property == “snakecaseProperty”){
//...do stuff
}
}
}
}
Why does this loop exist!!!!! All it does is remove any error checking if a getter method is misspelt...
To make matters worse the entire search method was over 300 lines building a MySQL query string.... even though there was an ORM and entity classes available!!!
rant
php #facepalm