Skip to content

Use camelCase instead of dash-case in HTML #4923

Closed

Description

@mhevery

With the new parser #4417 we should switch to no longer convert dash-case to camelCase and instead honor the properties as is.

Activity

  1. modified the milestone: on Oct 27, 2015
  2. Dzeks commented on Nov 5, 2015

    @Dzeks

    +1

  3. dpsthree commented on Nov 20, 2015

    @dpsthree
    Contributor

    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?

  4. Dzeks commented on Nov 27, 2015

    @Dzeks

    According to this commit
    a8edc1e#diff-c5fff3b58806e478f538ddb77868c5caR919
    inputs will be defined as

    inputs: ['aProp']

    but html will look like this

    <div [a-prop]="foo | bar"></div>

    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

  5. vicb commented on Dec 11, 2015

    @vicb
    Contributor

    adressed in #5765

  6. angular-automatic-lock-bot commented on Sep 7, 2019

    @angular-automatic-lock-bot

    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.

  7. locked and limited conversation to collaborators on Sep 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort2: daysfeatureLabel used to distinguish feature request from other issues

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions