emberjs/data — Issue #136: New naming convention could be a revision
Author: escalant3
Created: 2012-03-03 22:30:18+00:00
State: open

The naming convention commit_ https://github.com/emberjs/data/commit/75021dec2eeafb2d0f50d218e824bfa52b2456ef breaks all the applications that use the same notation in server and client.

I think that applying that behaviour by default without any notice is not the best option. At least it should be well documented, especially when it is only being applying to one part (associations are not been transformed at the moment).

I suggest applying the "revision:3" here cause it breaks applications backwards compatibility.