on naming arguments to functions

[reqshark]

more on why plus mad steeze like that on the example

[op1ekun]

Personally I use JSON to pass all my arguments there (I do it to avoid changing function's signature when I decide to add/remove some of the arguments later).
Usually I name this object "params".
When I pass this JSON object to constructor I call it "instanceParams".
All other stuff I pass as another object/array for example "flags". I try to use maximum of 2-3 arguments at once.

function foo(params, flags) {}

function MyClass(instanceParams, flags) {}

...and about naming arguments inside these object literals.
I usually try to describe them with one or two words (I use lower camelNotation), but I have NEVER called any one of them "data" ;)

I know that this is not the best answer, but maybe it will help :)

[hshoff]

Hi @reqshark my apologies for the delayed response.

I'm not sure if this is the right place to explain the arguments array that's automatically assigned to every function scope. I appreciate the details you're trying to add to clarify why naming a parameter arguments is a bad idea, but I think if we try to explain too much in one point it gets confusing.

It would probably be worthwhile to have a section dedicated to explaining the array-like arguments object.

🍻

[reqshark]

thanks @hshoff I appreciate that! Plus I totally agree, keeping it simple is always better than the risk of confusion. I almost always need to understand why the convention/pattern is a practice before I could roll with it and even hope to implement it in a meaningful way.