Skip to content

Switch to eslint and prettier #99

Open
@SleepWalker

Description

@SleepWalker

Let's do that!

I'm not agree with the rules, that standard js dictates, but this is another story. The reason why I suggesting this is because eslint + prettier will produce match more better dev experience. Standardjs has a slogan 'No decisions to make', but that is really not true.

If you look at standard docs or the code of logdown you will see eslint comments everywhere. So we are know exactly what decision was made and we are depending on that decision. According to this the standard lib has no sense. There is no encapsulation and moreover configs can not be completely avoided (e.g. ignore config), so in the end result standard is half-hearted solution (at least in the modern world). Better to use eslint directly (we can set up exactly the same rules). It will provide better IDE integration, because everyone has eslint extension installed. Another one good thing is that we will be able to remove /* eslint-env jest */ comments and use eslint overrides instead.

Additionally we can add precommit hooks, that will ensure, that we are commiting linted and pushing tested code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions