AccessTokenResponse contains non-standard attribute about sttp-oauth2

[majk-p]

I've looked into it, and it seems using generic solution described above might be an overkill. We might revisit this idea later, but I've prepared a PR fixing this specific issue in #114

[majk-p]

@vakhtang fix is now merged and released with v.0.11.0

[kubukoz]

Thanks for reporting!

Had a quick look, this seems to check out but I'll defer to the local expert @majk-p 😅

[vakhtang]

Thanks for the prompt response @kubukoz. I'm happy to open a PR for the change if we're all in agreement.

[majk-p]

Hi @vakhtang, thanks for the report! You are right that we don't follow the OAuth spec here, and we should fix that.
We were thinking about solution similar to this one: #104 introduced for AuthorizationCodeGrant. The bottom line would be to allow end user to specify the response type, while we'd provide a basic one (similar to OAuth2TokenResponse.Basic).
If you are willing to implement it that way, we are happy to accept a contribution 👍

[kubukoz]

@majk-p the default one should still be spec compliant, so we should probably make the field optional (and eventually remove it) anyway 😅

[majk-p]

On one hand it makes sense to go step by step, making the field optional. On the other hand both of those are breaking the API and we'd like to have as few of them as possible.