Skip to content

Fix Lints #230

Open
Open

Description

@bryanjos

There are a lot of them!

A good list to look at is here:
https://ebertapp.io/github/elixirscript/elixirscript

The "Quick Fixes" link shows the current list of lint issues

Activity

  1. bryanjos commented on Mar 5, 2017

    @bryanjos
    CollaboratorAuthor

    @jodylecompte thanks! Without any flags is fine I think. I would ignore the priv/std_lib/ directory for now. A file at a time is perfect!

  2. bryanjos commented on Mar 8, 2017

    @bryanjos
    CollaboratorAuthor

    @jodylecompte I've always had spaces in curly brackets on purpose. That should probably be configured to be ignored.

  3. added a commit that references this issue on Mar 8, 2017
  4. changed the title [-]Fix credo warnings[/-] [+]Fix Lints[/+] on Oct 2, 2017
  5. workingjubilee commented on Aug 18, 2019

    @workingjubilee
    Contributor

    Hello! Neat project! I was picking through the lint for the JS-end tests and I noticed a lot of them had "unexpected console statement". Seeing as how that lint rule is aimed at browsers, and most of the JavaScript that it's warning on is testing the ElixirScript and outputting legible data for our purposes, would you like that warning disabled in .eslintrc.js? It can be done just for certain files with the files and overrides keys.

  6. bryanjos commented on Aug 19, 2019

    @bryanjos
    CollaboratorAuthor

    Hi and yes that would be nice!

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