User Dashboard: Github Followers

[mikedao]

🚔 👮‍♀️ 👮‍♀️ 👮‍♀️ DO NOT START THIS STORY UNLESS THE STORY REFERENCED BELOW HAS BEEN COMPLETED BY BOTH IN YOUR PAIR.

You should pair on story "User Dashboard: Github Repositories" and deploy it prior to working on this one.

Continue this process for all stories labeled spike first. You will learn more this way and produce better code.

🚓 💨 👮 👮 👮

Details: A user exists in the database. They have a Github token stored. Generate a token here for testing and development: https://github.com/settings/tokens

A future story will implement generating these tokens dynamically but that isn't necessary here.

No need to hit the endpoint for followings. A future story will address this.

As a logged in user
When I visit /dashboard
Then I should see a section for "Github"
And under that section I should see another section titled "Followers"
And I should see list of all followers with their handles linking to their Github profile

API endpoint documentation https://developer.github.com/v3/users/followers/

• [x] API call uses authenticated call: /user/followers instead of /users/:username/followers
• [x] No hashes in the view.
• [x] Uses objects in the view to represent the followers.

[Mackenzie-Frey]

Other Steps - Post - Solo Spike:

• Integrate WebMock into other applicable Github Service Specs.
• Pull WebMock logic into ~rails_helper (per Josh's video @ ~23:00)
• Sad path feature testing - user sees only their own followers when other users have tokens (is this necessary to test?)

[Mackenzie-Frey]

Additional Steps:

• Alter headers so "GitHub" is larger than "Repos" and "Followers"
• Alter follower handles to have link to url.
• Add h3/h4 tags to list items for Repo names and Follower handles.