Standardize user_id condition
While creating a wrapper, I found the varying conditions for "user_id" to be frustrating and have resorted to creating a Map for subscription.type -> *_user_id condition. (broadcaster_user_id, from_user_id)
I think it would be easier to always have the condition be "user_id" for a user, and then allow a second property for modifying the scope of the condition. So in the instance of "users.follow", it might look like:
condition: {
user_id: "1337"
follow_source: "from"
}
What are your thoughts on this?
CoolViper24
shared this idea
-
Adminecressey
(Admin, Twitch)
commented
Hi CoolViper 24, thank you for the feature request. I'll second Syzuna's question: could you provide a little more detail on why this would be an improvement for you?
-
Syzuna
commented
I do not see the improvement on reducing mapping effort with that approach.
Maybe you can explain what kind of improvement you see with it?Also while Eventsub is not bound to Helix like Webhooks V1 were I think its a good idea to have some sort of consistency between the products here and maintain the to_user_id and from_user_id.