A small guide for naming stuff in front-end code

Re:A small guide for naming stuff in front-end code by stickfigure on Thursday January 13, 2022 @12:46PM (#29923945)

Another advantage of camelCase is that classNames (https://github.com/JedWatson/classnames) works without quoting:

    // you have a variable isFoo
    <SomeComponent className={classNames({isFoo})} />

is a lot better than:

    // you have a variable isFoo
    <SomeComponent className={classNames({'is-foo': isFoo})} />

(also, I personally shorten `classNames` to `cn` because it's so universally useful)

[ Parent | on HN ]

Re:A small guide for naming stuff in front-end code by seanwilson on Thursday January 13, 2022 @05:26PM (#29927814)

Yep, it would be nice if HTML/XML/CSS/Javascript/YAML/JSON/SQL identifiers were all standardised as it's not uncommon to see all of them in the same project.

[ Parent | on HN ]