node api
sakulstra opened this issue · 7 comments
i'm wondering why there's a dedicated ts-library (using request & bluebird :/), but no official types on sendinblue/APIv3-nodejs-library#57. Wouldn't it make sense to consolidate efforts over there?
We're currently considering migrating from mailchimp/gun to sendinblue where one argument for the migration was officially maintained wrapper apis :)
+1, we encountered huge complications while reading the API docs and trying to use this ts library. Why things can't be just simple? We'd rather not use this library.
+1, official types would be super welcome
Totally agree. This doesn't make any sense.
SendinBlue just autogenerate the SDK from Swagger standard... It's the main reason.
These repo are not "offcially maintained wrapper api" but just "dumping of autogenerated code on Github".. They are hard to use, badly documented and not really maintained
When I see the troubles using this package vs shooting a simple http request, I don't see the point.
The types are totally disjoint and allow nothing... useless...
Upgrading our app from node 8 to 12 and any deprecated dependencies. This is the only package that is impossible to get working and it's such a minor piece of our functionality. +1 for just setting type definitions than having a one off auto generated typescript library that is impossible to transpile.
It seems like having a Typescript dedicated library is just a marketing argument here, all the code is generated using a single tool from one single codebase so it's « easier » to maintain for the team. That's why you end up with such garbage code and documentation that is not clearly easy to take in hand and functionnal.
I highly recommend switching to SendGrid or any other provider that maintains a real user-friendly SDK. Or if you can't in short times, switch to the standard nodeJS library which is a bit less garage pill.