You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
rake aborted! ExecJS::ProgramError: Unexpected token: punc (:) (line: 1, col: 10, pos: 10) Error at new JS_Parse_Error (<eval>:2359:10623) at js_error (<eval>:2359:10842) at croak (<eval>:2359:19086) at token_error (<eval>:2359:19223) at unexpected (<eval>:2359:19311) at semicolon (<eval>:2359:19784) at simple_statement (<eval>:2359:22580) at <eval>:2359:20274 at <eval>:2359:19957 at block_ (<eval
backbone-ember-back-and-forth-transcript.txt �6i �U \T �U For those folks not already hanging out in #documentcloud... here's the log of this afternoon's Ember/Backbone politics discussion. 12:21 PM <wycats> how would you like me to describe backbone? 12:21 PM <wycats> let's work this out for once and for all :) 12:21 PM <wycats> I'm definitely not intentionally saying incorrect things about backb
Release 2.0.0 (August 20, 2015) Breaking Changes Usaved deleted records are no longer removed from hasMany relationships and RecordArrays returned by the store In Ember Data 1.13 once a record was marked as deleted it was removed from all of the RecordArrays and hasMany arrays it belongTo. This made it difficult to create UIs where a user could flag a record for deletion but still allow the user t
This is still work in progress. Adds a "Promise" tab to the inspector and displays a tree of Promises along with helpful debug info. This is possible thanks to @stefanpenner , @yapplabs, and @mhelabs for the idea and awesome work behind RSVP's instrumentation and the Promise Inspector. Create promise tree tab Create PromiseDebug which will use the Promise Assembler in @stefanpenner's Promise Inspe
Start Date: 2014-12-03 RFC PR: (leave this empty) Ember Issue: (leave this empty) The Road to Ember 2.0 Intro Today, we're announcing our plan for Ember 2.0. While the major version bump gives us the opportunity to simplify the framework in ways that require breaking changes, we are designing Ember 2.0 with migration in mind. This is not a big-bang rewrite; we will continue development on the mast
Currently, Ember apps must be downloaded in their entirety, evaluated, and executed before the end user sees any UI. Typically, most Ember apps serve a static "loading" page that is replaced by the framework when the app boots up. This can lead to degraded experiences as the user has to wait for JS and other assets to load before they get any actionable UI. The issue is exacerbated for mobile devi
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く