Skip to content

ng lint fails after ng new #624

Closed

Description

@johnpapa

I ran ng new foo then ng lint. There is a linting issue in the file below

$ ng lint
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.

> my-dream-app@0.0.0 lint /Users/john/_play/my-dream-app
> tslint "src/**/*.ts"

src/system-config.ts[35, 7]: variable name must be in camelcase or uppercase

Lint errors found in the listed files.

Activity

  1. added 3 commits that reference this issue on May 4, 2016
    9bbacdd
    3af15ba
    5d6cb5a
  2. added a commit that references this issue on May 4, 2016
    8467255
  3. angular-automatic-lock-bot commented on Sep 5, 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.

  4. locked and limited conversation to collaborators on Sep 5, 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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions