We have a use-case where we would like to query for the access scopes that are tied to an access token.
Slack does not currently provide any endpoints to service this need, instead they've included the scopes in the response header of every request made to slack under the X-Oauth-Scopes banner
Looking through the code, we seem to be only utilising header in the response here.
Do we have any strong opinions against returning the header for consumers further up the chain?
Having an opinionated approach on which endpoint we should use to service this use-case does not seem like the best thing to do since this requirement can be serviced by any Slack API endpoint.
However, thoughts on exposing this in a generic Do method to allow for customisation? (Haven't looked further in the code to see if this is possible, just spitballing.)
We have a use-case where we would like to query for the access scopes that are tied to an access token.
Slack does not currently provide any endpoints to service this need, instead they've included the scopes in the response header of every request made to slack under the
X-Oauth-ScopesbannerLooking through the code, we seem to be only utilising header in the response here.
Do we have any strong opinions against returning the header for consumers further up the chain?
Having an opinionated approach on which endpoint we should use to service this use-case does not seem like the best thing to do since this requirement can be serviced by any Slack API endpoint.
However, thoughts on exposing this in a generic Do method to allow for customisation? (Haven't looked further in the code to see if this is possible, just spitballing.)