`StandardTokenResponse` does not support twitch oauth response

[SarthakSingh31]

From dev.twitch.tv.

{
  "access_token": "rfx2uswqe8l4g1mkagrvg5tv0ks3",
  "expires_in": 14124,
  "refresh_token": "5b93chm6hdve3mycz05zfzatkfdenfspp1h1ar2xxdalen01",
  "scope": [
    "channel:moderate",
    "chat:edit",
    "chat:read"
  ],
  "token_type": "bearer"
}

The oauth response returns an array of scopes instead of a space delimited string of scopes.
The StandardTokenResponse only supports the space delimited string of scopes. It would be very useful if it supported both.

oauth2-rs/src/token/mod.rs

Lines 611 to 616 in 30ced32

	#[serde(rename = "scope")]
	#[serde(deserialize_with = "crate::helpers::deserialize_space_delimited_vec")]
	#[serde(serialize_with = "crate::helpers::serialize_space_delimited_vec")]
	#[serde(skip_serializing_if = "Option::is_none")]
	#[serde(default)]
	scopes: Option<Vec<Scope>>,

[ramosbugs]

From RFC 6749:

The value of the scope parameter is expressed as a list of space-delimited, case-sensitive strings.

This library adheres to the spec, which Twitch is not following.

See #52 and and #146 for suggested workarounds.

[ramosbugs]

The TL;DR is to implement the TokenResponse trait for a custom struct that matches Twitch's response. As the name StandardTokenResponse implies, it adheres to the standard. The reason the trait exists separately from the struct is to accommodate these scenarios.

[paulm17]

@ramosbugs is it possible for you to create an example? I'm able to get amazon, facebook, github, google, linkedin, microsoft, reddit, tiktok, twitter to work. But due to twitch not adhering to the spec. I'm completely stuck.

Thanks for your consideration.