-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Problem:
Review Opportunities API will decide whether a challenge is visible to a user by calling V3 Groups API, checking whether the groups of the current user belongs to including the group that is associated with the current challenge.
There is an iterative group api call here that in order to get all the groups the user belongs to
Solution:
We will migrate the calling groups-api to V5 and use a single api call to get all the groups the user belongs to.
Testing point:
-
Please take a benchmark performance testing in dev, the benchmark testing should tell a user who is belonging to many groups right now, take how much time to load the review opportunities list. So here the more groups that the user belong to, the better.
-
Please use the same testing criteria in dev after we deployed the changes regarding to use V5 Groups API, and note down how much time to load the review opportunities list.
By doing above two tests, I believe we can tell after our change, how much time we have improved by transferring to V5 Groups API.
Btw, reviewOpportunties API is used in the review opportunties page on Community App