-
Notifications
You must be signed in to change notification settings - Fork 9
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
Feature Request: Twitch login query for v3 GQL #65
Comments
I think a REST endpoint should be included as well with similar functionality. This would mean: v3 RESTEither have the same endpoint as v2 ( v3 GQLA query like userByLogin(login: String!): User that only takes the username - no user-id. |
The REST endpoint for querying by a twitch connection should resemble something like I don't currently see a use for querying by login or username, aside from convenience for testing, there are no valid use cases that I'm aware of for implementations. |
I was thinking of Chatterino though I just noticed it uses the twitch-id, so that's not really an issue (=> would need a GQL query + REST endpoint for querying by connection-id). For the webinterface it would be nice if you could go to a users profile by only knowing their name (when typing the URL) without going through user-search. Though query by connection-id is more important. |
I believe I have this issue, the few docs there are specify an endpoint for querying id by username, but it doesnt seem to be working. I need this for a TwitchBot that a user configures with their username, and looks up all 7tv emotes to give the bot access to for their channel. |
@starstormtwitch You can't currently by login, but you can by uid {userByConnection(id:"twitch_id"platform:TWITCH){emote_sets{emotes{data{name}name id}}}} Replace |
Yeah but if I don't have a way to programmatically look up the UID the
point is moot. Thanks though.
…On Fri, Oct 20, 2023, 4:25 PM Brian ***@***.***> wrote:
@starstormtwitch <https://github.com/starstormtwitch> You can't currently
by login, but you can by uid
{userByConnection(id:"twitch_id"platform:TWITCH){emote_sets{emotes{id name}}}}
—
Reply to this email directly, view it on GitHub
<#65 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVMU6GRH6Z3Q3OZKE5KOPFLYALT5JAVCNFSM55QEZ6F2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZXGM2DCNBRHE3A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@starstormtwitch This isn't to say this solves the issue, it would be nice for 7TV v3 to have login based querying, but with that being said. {user(login:"twitch_login"lookupType:ALL){id}} or if you need batching (this requires a first party cid) {users(logins:["twitch_login""twitch_login2"]){id}} or make a request to Twitch's Helix API (this requires a token with third party token scopes) to the following endpoint |
In v2 GQL, you could: Get a user by id, login or current authenticated user (@me).
Example:
https://old.7tv.app/users/brian6932 returns: https://old.7tv.app/users/60b04a7fad7fb4b50bd3a982
This is currently not possible with v3
https://7tv.app/users/brian6932 should return: https://7tv.app/users/60b04a7fad7fb4b50bd3a982
Problem being, this either generates unnecessary v2 REST requests, or forces people to use v2 GQL to query logins
The text was updated successfully, but these errors were encountered: