Blown away by how impossible it is to upgrade from Ember 1.0RC6 to 1.0.0. Maybe I'm just stupid, but it's utterly, utterly crippling.
-
-
Replying to @elliottkember
@elliottkember I’ve just done it so I feel your pain! :( Ember-data is just as bad. Have you read this? https://github.com/emberjs/data/blob/master/TRANSITION.md …1 reply 0 retweets 0 likes -
Replying to @CoatezyUK
@CoatezyUK all the way through. How'd you get on without App.Thing.find? I'm using that everywhere. My app's becoming a mess under 1.0!3 replies 0 retweets 0 likes -
Replying to @elliottkember
@elliottkember@CoatezyUK this.store.find should work. Why didn't it?2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@coatezyuk It was just for a login form, separate view. A pain for using the console though, what's the right way to inspect models?3 replies 0 retweets 0 likes -
Replying to @elliottkember
@elliottkember@wycats Now sorted everything is working great. I’m sure if I was more experienced with Ember I would have had less problems.2 replies 0 retweets 0 likes -
Replying to @CoatezyUK
@CoatezyUK@wycats like with modals, do I use the router? Do I initialise a view and let it create its controller? I need more hand-holding.1 reply 0 retweets 0 likes -
Replying to @elliottkember
@elliottkember@CoatezyUK the router + named outlet is the easiest approach for modals2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@CoatezyUK as in, what loads behind the modal when you refresh on that URL is unclear2 replies 0 retweets 0 likes
@elliottkember @CoatezyUK Nah. It doesn't relate to a URL. Named outlets can be controlled programmatically. Use actions in current route
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.