Feat: View Members List

[anitab-org]

Feat: View Members List

[mtreacy002]

@anitab-org/bridgeintech-maintainers . I have few technical challenges on this PR that I'd like to ask your advice on.

1. Any suggestion on how I can intercept the jwt token so user does not need to login to view the members list (send GET /users request to MS API)? Currently as per MS, this feature only available to login user. Should I modify to make this the same to BIT just for simplicity for now (so view members list is only enable to logged-in user)?
2. As you can see on the mockup (based on my original Mockup MVP) in this PR description, in members list I'd like logged-in user to be able to see members' email address so they have an alternative way to contact the member. However, MS API atm does not give that ability as GET /users/{user_id} does not return member's email. Is it ok if I also modified my MVP to not showing this (members email) for simplicity?
3. For @meenakshi-dhanani . Can you please direct me to where I can find an example of for loop within the html element that is not using DOM since I tried to use this for loop to create the rows in the members table from the data rerceived from backend respond. But all I can find in through googling is the for loop for HTML DOM which is not what we're using here.

[mtreacy002]

Update @anitab-org/bridgeintech-maintainers. I modified the Mockup in PR description by removing email and timezone to show user's availability instead which will be more meaningful information. Timezone is removed for 2 reasons:

1. location is enough to inform viewer the zone of the member is in
2. if timezone information need to be included, 2 api calls need to be made as timezone is part of GET /users/additional_info request which means slowing down performance.

[mtreacy002]

NOTE @anitab-org/bridgeintech-maintainers . Column Programs completed for this stage is not going to be shown as this is on be available after the users are involved in Programs, which means Organization, Program, and Mentorship Relation functionality need to be completed first for BIT to be able to do calculation on this column.

So, this column will be put as Icebox for now.
PS: the same goes to the Current Availability column (icebox for now till all other features completed)

[mtreacy002]

PS @meenakshi-dhanani. for quest.3, I found the solution. Will pushed the PR now. 😉