@ember-data/model

To help you get started, we've collected the most common ways that @ember-data/model is being used within popular public projects.

jelhan / croodle / app / models / user.js View on Github

/*
   * properties
   */
  // ISO 8601 date + time string
  creationDate: attr('date'),

  // user name
  name: attr('string'),

  // array of users selections
  // must be in same order as options property of poll
  selections: fragmentArray('selection'),

  // Croodle version user got created with
  version: attr('string', {
    encrypted: false
  })
});

View more ways to use @ember-data/model

Runtime Classes for use as a Schema Source and Resource Presentation for EmberData

Installation

Install using your javascript package manager of choice. For instance with pnpm

pnpm add @ember-data/model

Tagged Releases

Provides a Presentation Model for resource data in an EmberData Cache

This package implements the EmberData Store's instantiateRecord and teardownRecord hooks as well as configures an associated SchemaService implementation.

Models are defined as classes extending from import Model from '@ember-data/model'; and the attributes and relationships on these classes are parsed at runtime to supply static "schema" to EmberData's SchemaService.

Resource data for individual resources fetched from your API is presented to the UI via instances of the Models you define. An instantiated Model is referred to as a record.

When we refer to the ModelClass as opposed to a Model or Record we are referring specifically to the class definition and the static schema methods present on it.

When we refer to a record we refer to a specific class instance presenting the resource data for a given type and id.

Defining a Model

app/models/person.js

import Model, { attr, belongsTo, hasMany } from '@ember-data/model';

export default class PersonModel extends Model {
  @attr name;

  @belongsTo('pet', { inverse: 'owners', async: false }) dog;

  @hasMany('person', { inverse: 'friends', async: true }) friends;
}

modelName convention

By convention, the name of a given model (its type) matches the name of the file in the app/models folder and should be lowercase, singular and dasherized.