Support camelcase resolving of controllers in needs array

[rahulcs]

if a needs array contains a camel case name for a nested controller http://emberjs.com/api/classes/Ember.ControllerMixin.html#property_needs

This program fails on ember-app-kit because the resolver cannot find controller:postComment since it is not handled, which means discrepancy from the ember js syntax for needs.
http://emberjs.jsbin.com/iKAyIjIf/10/edit

[rwjblue]

I am unsure of this. I believe that you should be using needs: ['post/comment'] which should work properly with the current implementation. This would then resolve to the following paths (first wins):

app/post/comment/controller.js
app/controllers/post/comment.js

[rahulcs]

But this does not help someone following the documentation and using EAK and find it not working. Don't you think?

[stefanpenner]

EAK's naming conventions are a strict subset of embers, to prevent ambiguity. If anything we should assert if the usage is malformed.

ember 2.0 will be following these conventions, EAK is pushing everything forward.

[rwjblue]

@rahulcs - I agree that it is confusing, but the documentation does not specifically state that it needs to be camelized, and there are likely many examples in the documentation that will need to be fixed before we go live with this as the default resolver in Ember (likely 2.0).

[rwjblue]

@stefanpenner - So assert if decamalize(whatever) !== split[1].replace(/\./g, '/')?

[rahulcs]

Yeah at least an assert would be good if not a documentation change right away.
Let me know if I can push another commit for it. :)

[stefanpenner]

assert with a link to the new conventions
http://iamstef.net/ember-app-kit/guides/naming-conventions.html

[stefanpenner]

i thin kthose are up todate

[rwjblue]

@stefanpenner - OK, will work that up (with some tests).

[rahulcs]

The build is failing. Will send it again in some time.

[stefanpenner]

can you add a test?

[rahulcs]

@stefanpenner will add tests and commit.

[rwjblue]

You will only hit one since the other would require that you NOT hit an error.

[dogawaf]

Hi,
With ember data, I have now assertion thrown when lookup for 'model:staticContent'.
The only workaround that I found is to remove all underscores in my models...

[rwjblue]

@dogawaf - Can you give a bit more information on this in a new issue?

It would be helpful to have examples of your on-disk filenames (just the ones causing an issue), as well as how you are referencing them (if not by auto-lookup). It is quite possible that we need to tweak our assertions, but I'll need examples to add more test coverage.

[dogawaf]

My models directory:

app/models
app/models/static_content.js
app/models/profile.js
app/models/user.js

In my case, the lookup which fails the assert is done automatically by ember-data ActiveModelSerializer, which call store.modelFor('staticContent').
The JSON returned by the server contains the root object static_contents.

[rwjblue]

@dogawaf - #24