Get user profile

[anuveyatsu]

API for getting user profile information: /auth/get_profile?username=<username>

• new method get_profile_by_username in controllers
  • tests
• blueprint

[coveralls]

Coverage decreased (-0.5%) to 72.561% when pulling 3ca33b7 on feature/get-user-profile into 92b85ad on master.

[rufuspollock]

@anuveyatsu what issue does this relate to? Also what is the access restriction on this? And have you run it past @akariv ?

[akariv]

Hmm... not sure what this is going to be used for.
Anyway I don't think we'd like to expose the email address of all users via an api, no?

[anuveyatsu]

@akariv so probably we can expose some specific fields: username, userid, full name(?) and join_date. What do you think?

[akariv]

What's the purpose @anuveyatsu <https://github.com/anuveyatsu>?

…

On Thu, Aug 10, 2017 at 11:56 AM Anuar Ustayev ***@***.***> wrote: @akariv <https://github.com/akariv> so probably we can expose some specific fields: username, userid, full name(?) and join_date. What do you think? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAQMdUwIBHyn0-ViLHWlSvU3k4FuRVaNks5sWsXKgaJpZM4OzFzw> .

[anuveyatsu]

@akariv In the frontend, we want to show user profile information - joined_date (maybe some more in the future).

[akariv]

Okay - so yes, let's select exactly the fields that we want to expose publicly and only these should be returned in the API.

[anuveyatsu]

@akariv @rufuspollock so I will have these fields exposed:

• userid
• join_date

Please, confirm.

UPDATE: I suppose this is already minimal fields so I assume it is confirmed.

[coveralls]

Coverage decreased (-0.5%) to 72.561% when pulling 895ffd5 on feature/get-user-profile into 92b85ad on master.