-
Notifications
You must be signed in to change notification settings - Fork 49
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
v2: Rewrite SDK to automatically generate from latest docs #92
Conversation
Due to missing timestamp/signature in the query. There were even more issues when certain parameters are in the body vs in the query Looking at the postman collection, it just sends everything in the query so that looks to be okay?
@Cinderella-Man are you still monitoring this repo? Would love to hear some thoughts on this :) Not a full review needed but maybe you see something I’ve missed |
Hey @dvcrn I'm indeed getting tons of emails (one per your commit) about your updates. I sadly won't have time to review stuff this or next week. |
For every commit? 😄 Whoops that was a bit spammy
… On Jul 4, 2023, at 18:58, Kamil Skowron ***@***.***> wrote:
Hey @dvcrn <https://github.com/dvcrn>
I'm indeed getting tons of emails (one per your commit) about your updates. I sadly won't have time to review stuff this or next week.
—
Reply to this email directly, view it on GitHub <#92 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFIBRW2AB6JVKXI2YIYLUDXOPLJXANCNFSM6AAAAAAZ3KHUYU>.
You are receiving this because you were mentioned.
|
I've been using v2 for a while and it looks to be fine so far, so I'm going to cut v2.0.0 and update the default. I moved the previous master branch into a v1 branch so sticks around and we can roll back |
To improve maintainability and catch up with the latest changes to the Binance API, I rewrote everything with metaprogramming and learnings I made from ex_openai
Status: In Progress
Key changes:
Quirks:
any()
. For responses, we can manually map those. I backported everything that already existed in the tests, so all the existing structs are used as is and those endpoints have proper types. It's sadly a bit of a mixed bag now because some endpoints have proper structs while others don't:: xxxx.t()
) since we don't have them in the current structs yet. Need to either generate those or add them inpost_asset_get_funding_asset
)opts
when they shouldn'tFull list of functions with just the published spot collection. Others not included yet, but already way more than we had previously: