{"push_id":1478814251,"size":1,"distinct_size":1,"ref":"refs/heads/bug/overeager-dasherization","head":"30e95f8453b1f0bd4f507bc6186d30a665a2b3bb","before":"bd7fa875060795ac4bfe6204bcd4c4a861d28538","commits":[{"sha":"30e95f8453b1f0bd4f507bc6186d30a665a2b3bb","author":{"name":"Luke Melia","email":"20708a612f2164e970e0608bcf18a483ca8c8e72@lukemelia.com"},"message":"Don't resolve camelCase helper names to dasherized modules\n\nIn an Ember template, `{{someExpression}}` should NOT be\nrendered using a `some-expression` helper. Prior to this commit,\nit was. This led to a confusing experience where a local property\nwas not rendered because a dasherized helper of a similar name\nexisted.\n\nThis commit introduces a warning in debug mode when a camelCase\nhelper is looked up where the old behavior would have resulted\nin a dash-named module being returned but no longer does.\n\nThis warning should be removed in a future major release of this\npackage.","distinct":true,"url":"https://api.github.com/repos/lukemelia/ember-resolver/commits/30e95f8453b1f0bd4f507bc6186d30a665a2b3bb"}]}
{"actor":{"display_login":"lukemelia"}}