Merge pull request #1063 from bertdeblock/improve-ember-data-decorato…

…r-usage-examples

Use Ember Data decorators without parens where possible (#669)

guides/release/models/customizing-serializers.md

@@ -705,8 +705,8 @@ Ember Data's own `JSONAPISerializer` assumes types are plural and it
 will automatically singularize the types.
 
 Second, attribute and relationship names in the JSON:API document
-should exactly match the name and casing of the `attr()`,
-`belongsTo()` and `hasMany()`, properties defined on the
+should exactly match the name and casing of the `@attr`,
+`@belongsTo` and `@hasMany`, properties defined on the
 Model.
 
 By convention these property names are camelCase in Ember Data models.

guides/release/models/defining-models.md

@@ -47,9 +47,9 @@ import DS from 'ember-data';
 const { Model, attr } = DS;
 
 export default class Person extends Model {
-  @attr() firstName;
-  @attr() lastName;
-  @attr() birthday;
+  @attr firstName;
+  @attr lastName;
+  @attr birthday;
 }
 ```
 
@@ -64,8 +64,8 @@ import DS from 'ember-data';
 const { Model, attr } = DS;
 
 export default class Person extends Model {
-  @attr() firstName;
-  @attr() lastName;
+  @attr firstName;
+  @attr lastName;
 
   get fullName() {
     return `${this.firstName} ${this.lastName}`;
@@ -177,14 +177,14 @@ When the API returns a deeply nested, read-only object or array,
 there is no need to create multiple models with `attr('hasMany')` or `attr('belongsTo')`
 relationships. This could result in a potentially large amount of unnecessary
 code. You can access these objects in the template without transforming them. This can be
-done with `attr()` (No attribute type).
+done with `@attr` (No attribute type).
 
 The following example shows how to define these attributes without transforming them
 and accessing them within a template:
 
 ```javascript
-@attr() location;  // a read-only object
-@attr() tags; // a read-only array
+@attr location;  // a read-only object
+@attr tags; // a read-only array
 ```
 
 ```handlebars

guides/release/models/pushing-records-into-the-store.md

@@ -33,9 +33,9 @@ import DS from 'ember-data';
 const { Model, attr } = DS;
 
 export default class Album extends Model {
-  @attr() title;
-  @attr() artist;
-  @attr() songCount;
+  @attr title;
+  @attr artist;
+  @attr songCount;
 }
 ```
 

guides/release/models/relationships.md

@@ -186,7 +186,7 @@ import PaymentMethod from './payment-method';
 const { attr } = DS;
 
 export default class PaymentMethodCc extends PaymentMethod {
-  @attr() last4;
+  @attr last4;
 
   get obfuscatedIdentifier() {
     return `**** **** **** ${this.last4}`;
@@ -200,7 +200,7 @@ import PaymentMethod from './payment-method'
 const { attr } = DS;
 
 export default class PaymentMethodPaypal extends PaymentMethod {
-  @attr() linkedEmail;
+  @attr linkedEmail;
 
   get obfuscatedIdentifier() {
     let last5 = this.linkedEmail.split('').reverse().slice(0, 5).reverse().join('');
@@ -266,7 +266,7 @@ relationship. However, since readonly data will never need to be
 updated and saved this often results in the creation of a great deal
 of code for very little benefit. An alternate approach is to define
 these relationships using an attribute with no transform
-(`attr()`). This makes it easy to access readonly values in
+(`@attr`). This makes it easy to access readonly values in
 other objects and templates without the overhead of defining
 extraneous models.