-
Notifications
You must be signed in to change notification settings - Fork 499
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
Status of the Project? #469
Comments
@Xiphe I am wondering the same thing . . . I see some things being added via PRs that I would love to have access to! |
Ended up replacing this library with a manually generated client from Spotifys Open API spec using oazapfts oazapfts --optimistic https://developer.spotify.com/_data/documentation/web-api/reference/open-api-schema.yml ./spotify.api.ts Unfortunately, the auth flows are not part of that spec so I'll need to do that "by hand" but I can live with that as long as I have up to date methods & response types |
@Xiphe awesome! could you create a repo for this? |
@jpcastberg What would you hope to find in that repo? |
@Xiphe I ended up using the spotipy python library to do my project, was mainly looking for easy auth flow handling. If you're going to be adding better auth support in your openapi node library, it may be useful to others. |
The problem is spotify auth goes over a differen API which is not part of their OAS spec. So there's nothing oazapfts (or similar generators) can do about it. |
There is a new TS SDK for the web API now: https://github.com/spotify/spotify-web-api-ts-sdk |
Hey @thelinmichael huge thanks for this project, It helped me (and 18k other projects) interact nicely with spotify API!
I wonder what the status is since the last commit/release is nearly 2 years old and Issues+PRs are piling up.
Is there anything we can do to support?
The text was updated successfully, but these errors were encountered: