28 -- Camille Mauban

[cmauban]

• Yak Shaving
  • WIP Issue: 28 -- YOUR NAME
    • Links to PRs in:
      • USERNAME.github.io
        • journal-week-7 into master
        • feature/* into remodeling
        • remodeling into master
• Journal, Week 7
  • created journal-week-7 from master
  • flag in the sand for:
    • reflective journal
    • tutorial journal
    • bookmark journal
  • created feature branch x3: git flow feature start
• Reading APIs: Firebase & Restangular
  • Firebase REST API
    • What operations does the Firebase REST API support?
    • Do I need to authenticate with Firebase to read or create data?
    • What format does Firebase expect data to be in?
  • Restangular
    • How do I configure a REST-ful API like Github?
    • How would I request a list of...
      • ...Repos for the class Org?
      • ...Issues for the class Repo?
      • ...Issues for a specific Milestone?
  • ngRouter
    • How do I define...
      • ...a route for my application with ngRouter?
      • ...dynamic pieces (params) to routes?
      • ...the template to load for a route?
      • ...the controller to trigger for a route?
    • How do I retrieve...
      • ...the params from a route in a controller?
      • ...the controller for a route in the view?
• Don't Stop Believing
• GitHub Revolution: Angular Edition
  • git-flow that sucker!
  • angular-ize with bower and wiredep
  • just run the thing already!
  • $http.get ALL THE THINGS!
  • profile data angularized, cap'n!
  • at least one repo angularized, too!

Journal, Week 7: Any Way You Want It

Welcome to Week 8! Let's have a look back on Week 7 and your experience as Team Leaders. In your reflective journal this week, relate what you observed working as Team Lead yourself and working with a Team Lead. No need to name anyone; worry about what you've learned later. Get someone who wasn't on your team to review for you this week.

I'm sure there are some valuable tools and techniques you've leared over the last 7 weeks... How about a short tutorial journal? CSS grids are awesome? Write about 'em! Using Sass as a programming language? Tell us how! Just figured out how to make that tabbed panel interface exactly right? Share with the world!

While we're on the subject of tools, drop us a bookmark to one of them and write a little paragraph-long tl;dr on it.

Reading APIs: Firebase & Restangular

Firebase REST

We'll need somewhere to save our data for this week's application, and we don't have a ready API that can provide the data for us. Looks like we'll have to make our own with Firebase! Start with the Firebase REST API docs and delve into the supporting documentation as necessary.

• What operations does the Firebase REST API support?
• Do I need to authenticate with Firebase to read or create data?
• What format does Firebase expect data to be in?

Restangular

While we could totally use $http to interact with our Firebase apps, the Restangular library makes interacting with REST-ful APIs much easier. The whole API for Restangular fits in a single README, so start looking over that.

• How do I configure a REST-ful API like Github?
• How would I request a list of...
  • ...Repos for the class Org?
  • ...Issues for the class Repo?
  • ...Issues for a specific Milestone?

ngRouter aka angular-route

The simplest library for routing URLs to Controller code and loading templates is ngRouter, which comes as the angular-route package from Bower. Take some time to review the API for $routeProvider and the examples in the official documentation.

• How do I define...
  • ...a route for my application with ngRouter?
  • ...dynamic pieces (params) to routes?
  • ...the template to load for a route?
  • ...the controller to trigger for a route?
• How do I retrieve...
  • ...the params from a route in a controller?
  • ...the controller for a route in the view?

Don't Stop Believing...

Not quite done with your USERNAME.github.io layout? Identify at least 3 features that you intend to complete this week. Create or continue using feature/* branches with PRs into remodeling. Solicit peer reviews and merge your PRs as you go. Open a PR from remodeling into master so you can release your progress at the end of the week.

GitHub Revolution: Angular Edition

No one really liked that jQuery thing anyway. Start remodeling your TIY-GitHub using git-flow techniques: create a develop branch based on master and open a feature/shaping-up branch. In case you're missing it, npm install --save-dev bower wiredep to get those on your side and use bower install --save to add angular to your bower.json... make sure you have a bower.json first.

Use wiredep to link your shiny new copy of Angular JS (and any other bower_components for that matter) into src/index.html and confirm operation. Of course, Angular won't do much without a little more yak shaving, now will it? Create a new module named tiy-github in js/main.js inside an IIFE and attach that to your HTML with an ng-app Directive. Now watch all those placeholders go down the drain...!

In a simple run callback, load the $http and $rootScope service. Fetch and attach the data for Octocat and see what happens! Then start correcting your placeholders based on the cached API data. Make as much progress as you can, but don't let yourself get stuck on anything. Just make notes in your WIP Issue and bring them up in class. You should definitely have the basic profile info for Octocat and at least one repository filled in by Angular JS. Don't worry too much about the looks; that's not the point.

[cmauban]

JOURNAL-
cmauban/cmauban.github.io#30

GITHUB-
feautre/shaping-up into develop:cmauban/TIY-GitHub#20 have not merged

CMAUBAN.IO-
remodeling into master: cmauban/cmauban.github.io#32 have not merged
feature/basic-layout into remodeling:cmauban/cmauban.github.io#31
feature/hamburger-nav into remodeling:
feature/sidebar into remodeling:

[al-the-x]

Please review and close...