Skip to content

Code style ES2015 and beyond #1417

Closed
Closed
@dignifiedquire

Description

Warning the following content might be viewed as disruptive as it challenges currently used standards.

In most of my projects I've started moving the code use babel to leverage all new and nice things that ES2015 (was ES6) and some additional proposals bring. For me this brought a lot of clarity and general better code in every case. At the same time I've been removing semicolons. It's fine. Really! making the overall code even more clean.

As I know though these are some very personal preferences (at least the semicolons) so what do you think about it? Do you care or do you just want karma to work no matter what style it is written in 😉

// cc @karma-runner/contributors

Activity

dignifiedquire

dignifiedquire commented on Jun 26, 2015

@dignifiedquire
MemberAuthor

First step of moving to standard code style was done :)

kahwee

kahwee commented on Aug 16, 2016

@kahwee
Contributor

I was wondering about this when I was working on #2315. Babel and Standard makes such an essential combination to clean code for me.

dignifiedquire

dignifiedquire commented on Aug 16, 2016

@dignifiedquire
MemberAuthor

Well the code base was written way before standard, ES2015 & babel came to existence. The tests I moved to use babel and refactored them somewhat but moving the main codebase will be pretty big undertaking.

devoto13

devoto13 commented on Apr 11, 2021

@devoto13
Collaborator

This is done as the codebase uses both standard and modern JS syntax (without Babel though).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Code style ES2015 and beyond · Issue #1417 · karma-runner/karma