eadsjr / pgdoc Goto Github PK

I have a goal of simplicity of use for this library. Do you think using a single object parameter with named members as arguments to be extracted makes it more complicated?

Most things use positional arguments:

ex1( a, b, c )

This method uses destructuring internally to pick out named parameters.

ex2( { a, b, c } )

o = {}
o.a = a
o.b = b
o.c = c
ex3( o )

The issue comes up when I have a lot of parameters and you end up needing something like this.

ex4( a, null, null, null, null, b)

Which is annoying.

Also the single object style makes it easier to extend the function with backwards compatibility.

I just don't want to make it harder to use.

Is this something you would use or prefer? If so, why?

Because the initial examples were written in a synchronous context, a library implementing them will be very inefficient for any non-trivial application. A method of asynchronous handling should be decided and examples updated to match. This should happen before much code is written.