Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node api #5

Open
sakulstra opened this issue Oct 9, 2019 · 7 comments
Open

node api #5

sakulstra opened this issue Oct 9, 2019 · 7 comments

Comments

@sakulstra
Copy link

sakulstra commented Oct 9, 2019

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 :)

@digitalcortex
Copy link

digitalcortex commented Jun 11, 2020

+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.

@tgouala
Copy link

tgouala commented Jun 28, 2020

+1, official types would be super welcome

@MineiToshio
Copy link

Totally agree. This doesn't make any sense.

@RignonNoel
Copy link

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

@chevdor
Copy link

chevdor commented Jan 5, 2021

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...

@mikemcguire
Copy link

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.

@ScreamZ
Copy link

ScreamZ commented Sep 21, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants