seen from Taiwan
seen from United States
seen from Japan
seen from United States
seen from United Kingdom
seen from Japan
seen from United States
seen from United States
seen from China
seen from Switzerland
seen from Malaysia
seen from China
seen from Switzerland
seen from Ukraine
seen from Malaysia
seen from Malaysia
seen from United States
seen from United States
seen from Spain
seen from China
Ember-Tumblr v0.6.3
The latest version of Ember-Tumblr has been released! This new version brings the addon up to Ember-Data 1.13.11. Please test and let me know if there are any issues!
The addon has a shiny new demo page, too. Check it out here: github.jhawk.co/ember-tumblr
Coincidentally, my website has also been updated to E-D 1.13.11, so hopefully everything is still working. :)
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
EmberTricks[1]: Overwriting data store
Scenario:
I had a form that after submit could be modified on the backend. I needed to handle this and display the newly modified form.
Solution:
The success callback doesn't have any reference to status codes so I handled it in error
this.store.pushPayload is a pretty cool guy and will push a bunch of stuff into the store. A bunch of stuff is necessary. It will only push pluralized models in the payload. ie. users, posts not user, post. If you have any singulars you will have to munge the payload to pluralize the keys and wrap the data in an array.
Render the response as normal with an error status. I used code 409 to indicate a conflict
In the error callback you have access to an object that includes the status code and the response in responseJSON.
When the error is my custom status, I this.store.pushPayload(errorObject.responseJSON)
Now, this is the weird bit. I had the misconception that updating the models will overwrite the most recent changes as the "canonical changes" however this is not the case. Any changes you have made on the front end will still stick around. You actually need to record.rollback() for the model to reflect what you backend has returned.
