this post was submitted on 25 Nov 2023
37 points (95.1% liked)
Programming
17313 readers
607 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In PHP, a lot. Unit test are boilerplate 90% of the time, getters and setters (although they can be done via Generate), ORM classes with your default shebang (autoincrement ID), and I could go on and on.
I dislike snippets for code like "key this array by some logic" - this should be reusable via a dedicated helper or service.
Getters/setters can also be done automatically by
__get,__setor__callit's even possible to write a base class or trait that does this automatically.I am a PHP guru, if you've ever got questions I'm happy to help.
Sadly that's against best practices, it does not work with IDE autocomplete, and neither with PHPStan / PHPCS. You also don't get coverage from PHPUnit. And renaming a property does not rename the usage across the whole project.
__getand__setshould not be heavily used, and the project shouldn't be based on them.Some libraries, like Eloquent, uses them well, but you still need to annotate your class with
@propertyif you want to stay sane.Please never do any of this
Nah, it's actually very useful piping and makes code readable and useful.