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.

Sign up for GitHub

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

Jump to bottom

Is v1.1.1 safe from deprecation of using access_token as a quary parameter? #60

Open
terencechan8 opened this issue Jan 13, 2022 · 0 comments
Open

Is v1.1.1 safe from deprecation of using access_token as a quary parameter? #60

terencechan8 opened this issue Jan 13, 2022 · 0 comments

Comments

@terencechan8
Copy link

I'm using v1.1.1 of this library for my project and I found that it uses an authorization header which is the recommended way use access tokens as made in the announcement.

I'm just doing a quick sanity check to see if there are any other concerns about handling this deprecation I should be aware of?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@terencechan8