41
How do you manage code snippets?
(lemm.ee)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Nov 2023
41 points (95.6% liked)
Programming
17314 readers
9 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 !webdev@programming.dev
founded 1 year ago
MODERATORS
Please, can you give an example of such code snippets? I’m wondering what people consider reusable in different projects.
Seriously. A snippet library seems like a significant anti-pattern.
Not OP, but I'm thinking about the example in vs code: https://code.visualstudio.com/docs/editor/userdefinedsnippets
Some boilerplate code for libraries and frameworks I constantly use.
I'd be more interested in syncing the VS code snippets as they are automatically available in a file for each language and have the autocomplete stops.
If a library or framework requires boilerplate code it's a bad library or a bad framework.
I think this take is uneducated and can only come from a place of inexperience. There's plenty of usecases that naturally lead to boilerplate code, such as initialization/termination, setting up/tearing down, configuration, etc. This is not a code smell, it's just the natural reflection of having to integrate third-party code into your projects.
It depends how much boilerplate you need - there's obviously some stuff that needs to be the same all over but if there's significant amounts of code you constantly need to replicate that's when it's a code smell for me. I probably could've been more precise in my initial statement.
Yes, in my experience, boilerplate typically comes into play when you're using two libraries that don't know about one another, or have no business touching each other's concerns. (Using Alpine's
x-cloakwith Tailwind comes to mind.)That and every single
*-pipelines.yamlCI/CD config I've ever written.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.
Let’s say a function, about 20 lines. Something too small to warrant an external dependency but tricky enough that you don’t want to keep rewriting it.
I have things like a function to read through a file of newline delimited text of key-value pairs separated by whitespace. It skips comments (lines beginning with “#”), and returns the pairs. I’m happy to do a little copying instead of having a little dependency.
It is really really easy to make libraries.