Skip to content
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

Why there's a need for team:read scope? #55

Open
ivdma opened this issue Aug 21, 2017 · 0 comments
Open

Why there's a need for team:read scope? #55

ivdma opened this issue Aug 21, 2017 · 0 comments

Comments

@ivdma
Copy link

ivdma commented Aug 21, 2017

To answer my own question: it's because this gem fetches team_info and therefore needs a permission to do so.

But I wonder why team_info is required. I doubt that every single use-case would require team_info to be fetched from the API. Especially when the most of the basic information is already exposed through raw_info hash.

Shouldn't we make the team_info hash optional?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant