title: What is the convention for camelcase Model relationships in Ember?
body: <p>This is really a two-part question regarding model relationships in Ember.js</p>
  
  <p>First, it looks like the convention may have changed with the official release of 1.0, since the examples on the ember site use this convention:</p>
  
  <pre><code>App.Post = DS.Model.extend({
    comments: DS.hasMany('comment')
  });
  
  App.Comment = DS.Model.extend({
    post: DS.belongsTo('post')
  });
  </code></pre>
  
  <p>But I see a lot of examples from last year where code looks like this:</p>
  
  <pre><code>App.Post = DS.Model.extend({
    comments: DS.hasMany('App.Comment')
  });
  
  App.Comment = DS.Model.extend({
    post: DS.belongsTo('App.Post')
  });
  </code></pre>
  
  <p>So, part 1 is: <strong>Has this convention changed to what is on the Ember site currently, or are there reasons people are using <code>'App.Comment'</code>?</strong></p>
  
  <p>Part 2 has to do with the convention when using camel cased model names.</p>
  
  <p>Assuming the following:</p>
  
  <pre><code>App.Category = DS.Model.extend({
    //attributes
  });
  
  App.SubCategory = DS.Model.extend({
    //attributes
  });
  </code></pre>
  
  <p>I'm wondering what the convention is for setting up the relationships:</p>
  
  <pre><code>App.Category = DS.Model.extend({
    sub_categories: DS.hasMany('sub_categories')
    // or
    sub_categories: DS.hasMany('subCategories')
    // or
    subCategories: DS.hasMany('sub_categories')
    // or
    subCategories: DS.hasMany('subCategories')
    // or
    sub_categories: DS.hasMany('App.SubCategory')
    // or
    subCategories: DS.hasMany('App.SubCategory')
    // attributes
  });
  </code></pre>
  
  <p>Part 2 of my question is: <strong>Which of the above ways of writing the relationship is the convention? Or is there some other way I am not thinking about?</strong></p>