order-in-models.md

order-in-models

🔧 The --fix option on the command line can automatically fix some of the problems reported by this rule.

Note: this rule will not be added to the recommended configuration because it enforces an opinionated, stylistic preference.

Configuration

const rules = {
  'ember/order-in-models': [
    2,
    {
      // eslint-disable-next-line prettier/prettier
      order: [
        'spread',
        'attribute',
        'relationship',
        'single-line-function',
        'multi-line-function'
      ]
    }
  ]
};

If you want some of properties to be treated equally in order you can group them into arrays, like so:

// eslint-disable-next-line prettier/prettier
order: [
  'attribute',
  'relationship',
  ['single-line-function', 'multi-line-function']
];

Custom Properties

If you would like to specify ordering for a property type that is not listed, you can use the custom property syntax custom:myPropertyName in the order list to specify where the property should go.

Additional Properties

You can find the full list of properties here.

Description

You should write code grouped and ordered in this way:

1. Attributes
2. Relations
3. Single line computed properties
4. Multiline computed properties
5. Other structures (custom methods etc.)

Examples

// GOOD
export default Model.extend({
  // 1. Attributes
  shape: attr('string'),

  // 2. Relations
  behaviors: hasMany('behaviour'),

  // 3. Computed Properties
  mood: computed('health', 'hunger', function () {
    const result = this.health * this.hunger;
    return result;
  })
});

// BAD
export default Model.extend({
  mood: computed('health', 'hunger', function () {
    const result = this.health * this.hunger;
    return result;
  }),

  hat: attr('string'),

  behaviors: hasMany('behaviour'),

  shape: attr('string')
});

Help Wanted

Issue	Link
❌ Missing native JavaScript class support	#560