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.

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

Added two sections, covering RFCs #463 and #466 #84

Merged
merged 8 commits into from
Apr 19, 2019
Merged
Changes from 6 commits
Commits
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
27 changes: 21 additions & 6 deletions source/2019-04-12-the-ember-times-issue-94.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ responsive: true

This week:
calling nested components in angle brackets 🔍,
2 RFCs for improving Ember Data 💬,
user impersonation with ember-simple-auth 👤,
EmberCamp videos are live 🍿, ...

Expand Down Expand Up @@ -71,12 +72,26 @@ The best news? You don't have to wait till your app is at 3.10. Thanks to [@rwjb

---

## [Section Title in Title Case 🐹](#section-url)
<change section title emoji>
<consider adding some bold to your paragraph>

<add your name to author list, top and bottom>
<add blurb and emoji to "SOME-INTRO-HERE">
## [Record Data RFC: Record State 💬](https://github.com/emberjs/rfcs/pull/463)

In [RFC #463](https://github.com/emberjs/rfcs/pull/463), [@igorT](https://github.com/igorT) asks for **your help with improving the Record Data interface** in Ember Data.

What is Record Data? [Introduced in Ember 3.5](https://blog.emberjs.com/2018/10/15/ember-3-5-released.html), Record Data was designed to ...
ijlee2 marked this conversation as resolved.
Show resolved Hide resolved

- Help addons **extend Ember Data without relying on private APIs**
- Help apps **manage relationships, dirty attributes, rollbacks, and specialized models** via these addons

In the RFC, [@igorT](https://github.com/igorT) proposes that we add methods that return the `created` and `deleted` states of a record. These methods would be consumed by the addons to make correct decisions.

If you'd like to learn more, please take a look at [RFC #463](https://github.com/emberjs/rfcs/pull/463). Please also leave your feedback! ✍️

---

## [Ember Data RFC: Request State Service 💬](https://github.com/emberjs/rfcs/pull/466)

On a related note, [@igorT](https://github.com/igorT) proposes in [RFC #466](https://github.com/emberjs/rfcs/pull/466) that we create a **Request State service**, which returns the `in-flight` and `completed` states of a request. The service would, not only simplify how we determine the state of a request, but also help us work with data from multiple sources.

You can read more about the proposal in [RFC #466](https://github.com/emberjs/rfcs/pull/466). As always, feedbacks are welcome! 🙂
ijlee2 marked this conversation as resolved.
Show resolved Hide resolved

---

Expand Down