-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Support for RiotApi v4 #24
Comments
I'm waiting for it too, can help you with it Daniel if needed. |
Hi guys, there will be only minor adjustments to match |
In the end, I wll manage to fix the tests by myself. #25 should be priority now. |
@regiszanandrea, @boraguler library should support Also, the tests should be kind of working again. But definitely are not complete. So any additions are welcome. |
@dolejska-daniel Working as Designed. Thank you so much ❤️ |
Hey @dolejska-daniel, I'll create a new issue for Tournament V4 Support, it's ok? |
@regiszanandrea sure is! Didn't hear anything about Tournament v4 😮 |
@dolejska-daniel I think the only thing that will change is in the tournament code creation, passing the encrypted summonerId |
Hey guys! |
@dolejska-daniel Tournament v4 is available :) |
All |
@dolejska-daniel Love you ❤️ |
Is your feature request related to a problem? Please describe.
The Riot Developers announced that v3 API will be deprecated soon.
Describe the solution you'd like
Today, they made available the endpoints from the new API version, v4. In the link below, there are the endpoints that needed to be implemented:
https://developer.riotgames.com/api-methods/
The text was updated successfully, but these errors were encountered: