Feedback on usability.

[peebeejay]

I'm generally voicing displeasure about the change in function signatures in v8. Prior, one would invoke functions w a param object, while now, functions (ex: listTickers) can potentially have 15 different args that have to be passed in the correct order.

Given keyword arguments aren't a thing in typescript, usage here is unwieldy to the point of being dangerous and unusable.

Ex:

How was this design choice made? Clearly it will also impact upgradability and create a larger amount of breaking changes if function signatures change.

Looking forward to your response.

[peebeejay]

Sorry guys, but I feel there's a lot of room for improvement here. If the breaking changes in this latest version v8 were made in order to 'get the types in line with the spec' via auto gen types... I get the spirit & it makes sense to do that, but the implementation here leaves a lot to be desired.

[justinpolygon]

Hi @peebeejay, sorry for the delay on this. We weren't testing against endpoints with enough optional params to catch the mismatch between docs/examples and the actual positional args. Turn out we needed to change a default in the generator and we have released a breaking change with the latest release (run npm i @massive.com/client-js to update), where functions use a single request params object as shown in the examples. Here's the release notes https://github.com/massive-com/client-js/releases/tag/v10.0.0. All website examples should work as expected now.