Open Feerip opened 2 years ago
I haven't yet looked into the v6 API, but I will likely update it at some point in the near future.
On Wed, Apr 6, 2022 at 5:46 PM Phillip Smith @.***> wrote:
This doesn't seem to be working anymore, and I didn't do any extensive testing but it's probably because of Chamberlain's transition to their v6 API, as opposed to v5 being used in this project. Do you have plans to update the project to support API v6?
— Reply to this email directly, view it on GitHub https://github.com/JerrettDavis/MyQDotNet/issues/4, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAT5IF2XS37IDSO523OUR33VDYH4PANCNFSM5SXQPI6Q . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I'll be honest, I want this. Bad. So much so that I'm willing to help with work on it to make it happen. But I don't really know how or where to start :(
If you'd like to take a swing at it, one of the easiest ways is to look at one of the wrappers for another language, like this python one, and see how their API layer differs from mine. Unfortunately, I haven't had any time to dedicate to this project.
Okay, I’ll take a look, thanks!
From: JD Davis @.> Sent: Wednesday, April 20, 2022 6:23 AM To: JerrettDavis/MyQDotNet @.> Cc: Phillip Smith @.>; Author @.> Subject: Re: [JerrettDavis/MyQDotNet] API v6 transition? (Issue #4)
If you'd like to take a swing at it, one of the easiest ways is to look at one of the wrappers for another language, like this python onehttps://github.com/arraylabs/pymyq, and see how their API layer differs from mine. Unfortunately, I haven't had any time to dedicate to this project.
— Reply to this email directly, view it on GitHubhttps://github.com/JerrettDavis/MyQDotNet/issues/4#issuecomment-1103927881, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACF4JAIKZEJ6OLUV4O4W2JDVGAAONANCNFSM5SXQPI6Q. You are receiving this because you authored the thread.Message ID: @.***>
This doesn't seem to be working anymore, and I didn't do any extensive testing but it's probably because of Chamberlain's transition to their v6 API, as opposed to v5 being used in this project. Do you have plans to update the project to support API v6?