Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ember Data JavaScript Modules API #238

Closed
wants to merge 6 commits into from
Closed

Ember Data JavaScript Modules API #238

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
2083413
Create 0000-ember-data-javascript-module-api.md
locks Jul 25, 2017
dd5d9b5
Update 0000-ember-data-javascript-module-api.md
locks Jul 25, 2017
ac5c0b6
Update 0000-ember-data-javascript-module-api.md
locks Jul 25, 2017
8b5d114
Update 0000-ember-data-javascript-module-api.md
locks Jul 25, 2017
b4e9031
Update 0000-ember-data-javascript-module-api.md
locks Jul 25, 2017
1496320
Update 0000-ember-data-javascript-module-api.md
locks Jul 25, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update 0000-ember-data-javascript-module-api.md
  • Loading branch information
@locks
locks authored Jul 25, 2017
commit 1496320fe672545e917cadaf905c4e8d153a62b3
9 changes: 3 additions & 6 deletions text/0000-ember-data-javascript-module-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,8 @@ This document proposes changes to the modules exported by Ember Data to make it

# Detailed design

Ember Data will stick with 1 top level namespace of `@ember-data`. Under it there are 6 nested module
namespaces where exposed components could live. Someday these namespaces could be moved into their own
top level scoped package (for example `@ember-data/serializer` could become `@ember-data/serializer`) however,
that is not being proposed at this time.

Ember Data will stick with 1 top level namespace of `@ember-data`.
Under it there are 6 nested module namespaces where exposed components could live.

- `@ember-data/store` - Store related concers with storing records inside ember data's identity map.
- `@ember-data/model` - Classes and utilities related to modeling data
Expand Down Expand Up @@ -108,7 +105,7 @@ byt theyhave their own name and namespace in the Ember container.
| Global | Module |
|--- | --- |
| `DS.Serializer` | `import Serializer from '@ember-data/serializer'` |
| `DS.EmbeddedRecordsMixin` | `import EmbeddedRecordsMixin from '@ember-data/serializer/src/embedded-record-mixin'` |
| `DS.EmbeddedRecordsMixin` | `import EmbeddedRecordsMixin from '@ember-data/serializer/src/embedded-records-mixin'` |
| `DS.JSONAPISerializer` | `import JSONAPISerializer from '@ember-data/serializer/src/json-api'` |
| `DS.JSONSerializer` | `import JSONSerializer from '@ember-data/serializer/src/json'` |
| `DS.RESTSerializer` | `import RESTSerializer from '@ember-data/serializer/src/rest'` |
Expand Down