With the new parser #4417 we should switch to no longer convert `dash-case` to `camelCase` and instead honor the properties as is.
Activity
Dzeks commentedon Nov 5, 2015
+1
dpsthree commentedon Nov 20, 2015
Just to clarify, if you write or [my-prop] on a template, what identifiers would be expected as the component selector and the input property?
Dzeks commentedon Nov 27, 2015
According to this commit
a8edc1e#diff-c5fff3b58806e478f538ddb77868c5caR919
inputs will be defined as
but html will look like this
so now it's a bit confusing
and for some reason events are still parsed to camelCase
(some-event) will be someEvent
all events with dashes will be ignored
vicb commentedon Dec 11, 2015
adressed in #5765
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.