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
Next Next commit
Update 0000-ember-data-javascript-module-api.md
  • Loading branch information
@locks
locks authored Jul 25, 2017
commit ac5c0b65955cf4928821b61b18ea54fab133b5e1
16 changes: 11 additions & 5 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,13 +12,19 @@ This document proposes changes to the modules exported by Ember Data to make it

# Detailed design

The

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,
Ember Data will stick with 1 top level namespace of `@ember-data`. Under it there are 6 nested module
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why @ember-data instead of @ember/data as proposed in https://emberjs.com/blog/2017/04/05/emberconf-2017-state-of-the-union.html#toc_ember-in-2017?

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,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the difference between @ember-data/serializer and @ember-data/serializer?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bad edit from the draft.

that is not being proposed at this time.


- `@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
- `@ember-data/adapter` - Classes and utilities related to communicating with external backends
- `@ember-data/serializer` - Classes for serializing and extracting data from outside Ember Data
- `@ember-data/transform` - Classes for transforming individual values
- `@ember-data/promise-proxies` - Classes for allowing promises to show up in ember templates.

# How We Teach This

What names and terminology work best for these concepts and why? How is this
Expand Down