Little confusion in the docs - controllers: "model property"? "content property"?


#1

The guides at emberjs.com/guides seem to mesh together the terms “content property”, and “model property”. I would have raised a bug - except I’m not so sure. Is this merely a typo? Or could we simply just standard on one term, and just call it that, instead of calling it by 2 different names?

You can see this in http://emberjs.com/guides/routing/specifying-a-routes-model/, and http://emberjs.com/guides/routing/setting-up-a-controller/ (grep for ‘model property’)

Note: if it truly is a typo, I’d be glad to file it as a bug. But thought to check in here first.


#2

I don’t think it’s really a bug, since in the controller they mean the same thing. But having two different words for the same thing makes it confusing, and doesn’t help with the docs.

There’s still no consensus on which property should prevail (or even if both). More info here: https://github.com/emberjs/ember.js/issues/2007


#3

got it. Thanks! Glad to see that it’s not just me…


#4

I saw @tom comment on an issue on GitHub and say, model == content and that model is the preferred property to use but for backwards compatibility content will be there for the time being.


#5

#6

thanks, guys! That clears it up for me very nicely. And i’m glad that we’re sticking with model!