-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
feat(api): Allow fetching team details without projects #13935
Conversation
This allows you to fetch team details that do not include projects, which improves performance.
4405a5c
to
71f52d2
Compare
@@ -81,6 +81,7 @@ def get(self, request, organization): | |||
|
|||
:pparam string organization_slug: the slug of the organization for | |||
which the teams should be listed. | |||
:param string detailed: Specify "0" to return team details that do not include projects |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would a better name be sparse
? And then it can do the inverse here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use detailed
elsewhere, and I think that makes sense in terms of how we'd like our API to behave. Ideally our default behaviour becomes not detailed, and people have to explicitly ask for detailed, and so pass detailed=1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See this thread #13925 (comment)
@@ -81,6 +81,7 @@ def get(self, request, organization): | |||
|
|||
:pparam string organization_slug: the slug of the organization for | |||
which the teams should be listed. | |||
:param string detailed: Specify "0" to return team details that do not include projects |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use detailed
elsewhere, and I think that makes sense in terms of how we'd like our API to behave. Ideally our default behaviour becomes not detailed, and people have to explicitly ask for detailed, and so pass detailed=1
This allows you to fetch team details that do not include projects, which
improves performance.