GraphQL API for group and project membership
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The following discussion from !21496 (merged) should be addressed:
-
@nick.thomas started a discussion: (+3 comments) It looks like we don't have a graphql API for membership yet, so there's no need to add this attribute there
👍 .Maybe it's something we should think about adding soon though; then clients would be able to avoid the expense of calculating this attribute if they don't want it.
In certain other REST API endpoints, we do allow people to say "include this attribute", or "exclude this attribute". Do you think this is a pattern worth following here? To me it feels like this attribute isn't often going to be what people are interested in, so we could only include it in the response
if params[:include_seat_info], or something similar?