Don't use flags as function parameters #235

kanalasumant · 2017-12-04T03:37:09Z

Thanks for this wonderful curation of clean coding practices. I don't have so much as an issue but I'm unable to wrap my head around this rule, as to how does one split the function into two functions without actually knowing the value of temp which can be only be known with an if statement. This seems like I should use polymorphism but my question is about this particular issue as to how the functtion createFile got separated into two functions without the conditional check. I'd appreciate if anyone can throw some light on this.

jljorgenson18 · 2017-12-04T07:07:52Z

The code that is calling createFile at a higher level should be figuring out which one of the two functions to call. If there are two completely different and non-intersecting blocks of code in a function, then chances are that the function is not just doing one thing. If you were to expand the fs.create blocks in the function to be 20 lines long each, things may make more sense on why you would want to split them.

kanalasumant · 2017-12-04T15:12:00Z

Hmm, so at the higher level, one would probably use an if statement anyway to determine which call. Sounds good. Will try it. Thanks @jljorgenson18 !

ryanmcdermott / clean-code-javascript

Don't use flags as function parameters #235

Don't use flags as function parameters #235

kanalasumant commented Dec 4, 2017 •

edited

jljorgenson18 commented Dec 4, 2017

kanalasumant commented Dec 4, 2017

ryanmcdermott / clean-code-javascript

Join GitHub today

Don't use flags as function parameters #235

Don't use flags as function parameters #235

Comments

kanalasumant commented Dec 4, 2017 • edited

jljorgenson18 commented Dec 4, 2017

kanalasumant commented Dec 4, 2017

Essential cookies

Always active

Analytics cookies

kanalasumant commented Dec 4, 2017 •

edited