Programming

17319 readers

150 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

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

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

If a parameter isn't used, what should I pass? - The Old New Thing (devblogs.microsoft.com)

submitted 8 months ago by SmartmanApps@programming.dev to c/programming@programming.dev

11 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] hightrix@lemmy.world 19 points 8 months ago (1 children)

The answer, as with everything in software development, is that it depends.

A god method with 100 optional params that is usually bad practice. But a common pattern is to allow for an options object to be passed, and that object may contain 0-n supported parameters. This pattern is used everywhere, see graphql as a widely used library that is based on this.

[–] bungle_in_the_jungle@lemmy.world 7 points 8 months ago

Totes this. I've refactored far too many of these things in my day so I just about always reach for an options object if there's the slightest uncertainty about adding more params in the future.