33--Look-at-all-the-Comments-last :( Ari Gonzalez

[AriGonzo]

Review

Today we looked at Yeoman, generators, and kickstarters like HTML5 Boilerplate and Angular Kickstart. The generators attempt to follow and enforce the Angular Best Practice for App Structure: breaking down applications into discrete feature modules.

In class, we used generator-gulp-angular to start a new Angular JS project -- a Twitter clone that uses the Github API to store our comments -- using Gulp, Bower, and Bootstrap. We talked about the problems with authentication and authorization and used OAuth to get a token from Github for use with our application.

Shaping Up with Angular JS, Take 3!

Work through Level 2, 3, and 4 tonight, same rules as yesterday. You should be able to breeze through level 2 on your own, but the concepts in 4 will be fuzzy. Plow through by buying answers and typing them to proceed! Don't get bogged down!

Look at all the Comments!

Using our in-class project as a reference, build your own Github-powered Twitter site. It should satisfy all the following User Stories, have a PR to your TIY-Assignments:master branch, and be deployed to your TIY-Assignments Github Pages. Include a link to the page in your WIP issue and link the PR to your WIP issue as usual. MAKE TODOS FOR YOURSELF!!

To Do:

• Configure controller to pull API information for WIP Issue
• From the API - Get the following information for existing comment:
  • Commenter login name linked to the profile
  • Comment body
  • Comment avatar
  • datetime of comment
• Wire up the authentication check
• Configure the POST setting to post to the WIP issue
• Update the current view with the post
• Limit comments to 140 characters
• Comments should render Markdown
• Allow editing comments within 2 minutes
• Lock out editing after 2 minutes
• Only allow edits on comments you have made

---

I can post a comment so that I can express my opinion on the internet.

• Comment text is restricted to 140 characters in length.
• You must supply a OAuth token to identify yourself.
• The new comment should be added to the page and your WIP issue in the class repository.

I can see the list of all previous comments so that I can read the opinions of others.

• Show the name of the user who wrote the comment, their avatar (appropriately sized), and link to their Github profile.
• Include the date and time that the comment was last updated.
• The body of the comment should render any included Markdown syntax.
• All comments added to your issue via Github should also appear on your page.

I can edit a comment that I have previously made so that I can correct typos or adjust formatting.

• There should be a UI element on a comment that makes it "editable".
• The UI element should be disabled for comments that I didn't create (need a hint?)
• If the comment is more than 2 minutes old, I cannot edit it (on your page).

[AriGonzo]

Oh hey look! Comments!

[AriGonzo]

It worked! Thank the sweet baby jebus, it worked!

[AriGonzo]

test test test

[AriGonzo]

http://arigonzo.com/TIY-Assignments/YeomanProject/dist/

[AriGonzo]

AriGonzo/TIY-Assignments#22

[thedonz]

THE FORCE IS STRONG WITH YOU, ARIGONZO