26 -- J.R. Worley

[jeffworley]

• [x] Yak Shaving
  • [x] WIP Issue with links to:
  • [x] your PRs in USERNAME.github.io
  • [ ] your PRs in TIY-GitHub for features and releases
  • [x] your PRs in TIY-Catalog for feature--* into develop
  • [x] WIP Branch:
  • [x] USERNAME.github.io:journal-week-6
  • [ ] TIY-GitHub:
    • [ ] release--* -- if you're ready for another release
    • [ ] feature--* -- for any new features
  • [x] TIY-Catalog:
    • [x] feature--* -- for any feature you're working on
• [x] Journal, Week 6
  • [x] Resource BEEN DONE.
  • [x] Reflective done by Thu!
  • [x] Tutorial drafting...
• [ ] Reading APIs: Etsy
• [x] Shaping Up with Angular JS
  • [x] Level 2 complete (again)!
  • [x] Level 3 complete!
  • [x] Pics or it didn't happen!
• [ ] The Man with the Golden GitHub
• [x] Etsy Goes Marching On

  26 -- API Another Day

  Journal, Week 6

You know what to do. Tomorrow you should have your final draft of your Reflective journal and some rough drafts for your Tutorial journal. Your Reosource post was done already. Right?

Reading APIs: Etsy

The data from your page has to come from somewhere in the API, right? Well, the trick here is that the way the data is represented in the API may not precisely match the way it's presented on the page. You'll want to research the following questions:

• For the product list (category) page what data is needed from...
  • the Listing resource?
  • the ListingImage resource?
  • the Variations_* resources?
  • the Category resource?
  • the Shop resource?
• On the product detail page what data is needed from...
  • the Listing resource?
  • the ListingImage resource?
  • the Variations_* resources?
  • the Category resource?
  • the Shop resource?
• Identified for each:
  • API endpoint
  • required query params
  • additional params needed (fields, includes)
  • sample data returned

Make a sample request using Postman or curl to inspect real responses from the API to verify your hypotheses from the documentation. These findings could be valuable to your team!

Shaping Up with Angular JS: Round 2

Continuing with our exercise with Angular JS, work through levels 2 (again) and 3 of Shaping Up on CodeSchool. Try to work through the challenges on your own, but don't get bogged down.

The Man With the Golden GitHub

Keep building your Responsive GitHub page. Tonight, try to get the tablet view done. After merging, cut a new release--* branch from master and a new branch from that called feature--responsive-tablet.

Etsy Goes Marching On

Time to switch Team Leads!

If you're the new lead, no coding for you! You must support the other two team members with planning, API reading, data analysis, and code review. Look over their shoulders and help them avoid painful syntax errors and split your time between them. There's plenty to do without writing anything.

If you were the lead, pick up one of the existing, open tasks before starting a new task. That doesn't have to be the new lead's old task, either. If your third teammate is stuck on something: trade. Rely on your new Team Lead for direction and support.

Between the three of you, you should tackle at least one feature per person with HTML, (S)CSS, and some Angular JS placeholders. With your new knowledge of the Etsy API and the $http service, load some data from your cache in apis/etsy/ and pull it into your page to replace some placeholders.

[jeffworley]

Listing Page: Body Grid Pt2 PR: https://github.com/TIY-Durham/TIY-Catalog/pull/57

Listing Page: Image Slider PR: https://github.com/TIY-Durham/TIY-Catalog/pull/58

Journal Week 6 PR: https://github.com/jeffworley/jeffworley.github.io/pull/34

EtsyAPI PR: https://github.com/jeffworley/tiy-assignments/pull/41

[jeffworley]