e77becb59e
The fix here is two fold: - We shouldn't be providing the DataSource (which loads the data) with an id when we are creating from within a folder (in the buggy code we are providing the parentKey of the new KV you are creating) - Being able to provide an empty id to the DataSource/KV repository and that repository responding with a newly created object is more towards the "new way of doing forms", therefore the corresponding code to return a newly created ember-data object. As we changed the actual bug in point 1 here, we need to make sure the repository responds with an empty object when the request id is empty. |
||
|---|---|---|
| .. | ||
| components | ||
| dc | ||
| settings | ||
| steps | ||
| deleting.feature | ||
| index-forwarding.feature | ||
| login-errors.feature | ||
| login.feature | ||
| navigation-links.feature | ||
| page-navigation.feature | ||
| startup.feature | ||
| submit-blank.feature | ||
| token-header.feature | ||