-
Notifications
You must be signed in to change notification settings - Fork 20
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
Proposal of evolution for the library #25
Comments
@CalebAlbers Thanks for pinging us on this. Let me admit right away that I am hopelessly behind the times on Node JS development, so please forgive any weird questions I might ask until I can find some internal experts to get their thoughts. We do want to make our clients useful and easy for as many developers as possible. So in that light, could this change cause problems for anyone? For instance, is the Promise format only available after a certain version? Are there commonly used frameworks that don't support it? Would this be a backwards compatible change that users can simply drop in without updating their application code? etc. etc. I would love to get with the times, but as long as it doesn't cause problems for anyone that's been using the client as-is. |
@AaronAtDuo if you check out my old PR (#22) you will see I have been using this in production and it's compatible with your existing code. Promises are standard in all of the currently supported versions of NodeJS. I can make a new PR and clean it up a bit since my newer production code we use is even further updated. I think there were some auto-formatting issues in my last one. I designed the update so that all of the existing calls are left intact and the new calls just use a promise version of the existing calls. |
@AaronAtDuo. Ready to go: #31 |
For anyone interested I have started my own package for this API. It’s available here: https://www.npmjs.com/package/duo-admin-api |
Please accept this modest contribution to make your library support Promise format.
This is what I add after the lib import to be able to use it in async/await
That can then be used nicely as follow
The text was updated successfully, but these errors were encountered: