-
Notifications
You must be signed in to change notification settings - Fork 33
[$20] Remove support of enrich
query param for GET /taas-teams/me
endpoint
#170
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
Comments
Challenge https://www.topcoder.com/challenges/3fe7d3a3-c9de-4252-b766-f162ebc687bb has been created for this ticket. |
GET /taas-teams/me
endpointenrich
query param for GET /taas-teams/me
endpoint
@imcaizheng would you like to pick up this? |
enrich
query param for GET /taas-teams/me
endpointenrich
query param for GET /taas-teams/me
endpoint
@imcaizheng I had to revert PR for adding You can revert my revert again in your branch and after update it as per this issue description. I hope it's not confusing. |
Challenge https://www.topcoder.com/challenges/3fe7d3a3-c9de-4252-b766-f162ebc687bb has been assigned to aaron2017. |
Payment task has been updated: https://www.topcoder.com/challenges/3fe7d3a3-c9de-4252-b766-f162ebc687bb |
We found an issue with using
enrich
query param ofGET /taas-teams/me?enrich=
endpoint, see #154 (comment).So we have to remove support of
enrich
for theGET /taas-teams/me
endpoint. And we always have to get user data from u-bahn withenrich=true
.enrich
query param from API, Swagger, Postman, Joi, and so on.enrich=true
if we filter byexternalProfile.externalId
The text was updated successfully, but these errors were encountered: