-
Notifications
You must be signed in to change notification settings - Fork 139
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
Standardised skills when creating gigs, and removal of TaaS App links #4605
Conversation
feat: upgrade to v5 member api
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
+ encodeURIComponent(fields) | ||
+ `&query=${encodeURIComponent(query)}` | ||
+ '&limit=' + userIds.length | ||
const fields = 'userId,handle,photoURL,firstName,lastName' |
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.
It's not clear to me what all of these changes are related to -- can you fill me in?
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 had to update our usage of the member API from v3 to v5, which was a separate problem. This was related to that change and just some slight differences between the versions.
JIRA: https://topcoder.atlassian.net/browse/TSJR-230
Supports: https://topcoder.atlassian.net/browse/TSJR-61
https://topcoder.atlassian.net/browse/TSJR-178
https://topcoder.atlassian.net/browse/TSJR-162