<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ember-Data on John Hamelink</title>
    <link>https://johnhame.link/tags/ember-data/</link>
    <description>Recent content in Ember-Data on John Hamelink</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>John hamelink</copyright>
    <lastBuildDate>Sat, 28 Feb 2015 21:39:00 +0000</lastBuildDate>
    <atom:link href="https://johnhame.link/tags/ember-data/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Consuming Nested API Routes with Ember</title>
      <link>https://johnhame.link/posts/consuming-nested-api-routes-with-ember/</link>
      <pubDate>Sat, 28 Feb 2015 21:39:00 +0000</pubDate>
      <guid>https://johnhame.link/posts/consuming-nested-api-routes-with-ember/</guid>
      <description>&lt;p&gt;At the time of writing I&amp;rsquo;m learning Ember-cli for the first time. It&amp;rsquo;s pretty&#xA;tough as there&amp;rsquo;s not too much up-to-date documentation out there, but I&amp;rsquo;m&#xA;slowly getting there, and I&amp;rsquo;m beginning to feel the power it brings.&lt;/p&gt;&#xA;&lt;p&gt;One of the things I&amp;rsquo;ve been finding especially difficult is grokking how&#xA;Ember consumes API data - specifically how it decides upon what the route&#xA;it wants to consume looks like.&lt;/p&gt;&#xA;&lt;p&gt;After hours of fruitless Googling and reading, I relented and hit IRC:&#xA;#emberjs on Freenode to be specific. After speaking to a few helpful fellows&#xA;on there, it became clear that Ember was not easily able to consume nested API&#xA;routes just yet. Damn! That makes scoping your API data quite hard!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
