Skip to content

Shared tslint and tsconfig #174

Description

@bajtos

In the spirit of eslint-config-loopback, we should move our tsc and tslint configuration to a shared package that can be used by other LoopBack.next projects, e.g. loopback-next-example.

cc @ritch @superkhau

Activity

  1. self-assigned this
    on Apr 19, 2017
  2. superkhau commented on Apr 19, 2017

    @superkhau
    Contributor

    Any ideas for the name of the package? Does tslint provide conventions like http://eslint.org/docs/user-guide/configuring#using-a-shareable-configuration-package?

  3. added
    developer-experienceIssues affecting ease of use and overall experience of LB users
    and removed on Apr 19, 2017
  4. bajtos commented on Apr 20, 2017

    @bajtos
    MemberAuthor

    I am proposing @loopback/tsling-config

    tslint does provide conventions for sharing rules, see sharable-configuration-rules. In the post, they are using shared-tslint-rules as the project name. Other people seem to use tslint-config-{name}, see e.g.

    BTW we may want to consider using some eslint rules via https://github.com/buzinas/tslint-eslint-rules, but that's out of scope of this patch. OTOH, I personally think we should move to Prettier (see #165) and configure tslint only to check for programming errors only.

  5. superkhau commented on Apr 20, 2017

    @superkhau
    Contributor

    Prettier looks nice, I like the philosophy. +1

    I'm fine with @loopback/tsling-config.

    Using some ESLint rules is fine, we can address those when they actually come up.

  6. dhmlau commented on Sep 6, 2017

    @dhmlau
    Member

    relate to: #165

  7. bajtos commented on Dec 15, 2017

    @bajtos
    MemberAuthor

    Closing as done by #682

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

Metadata

Metadata

Assignees

Labels

developer-experienceIssues affecting ease of use and overall experience of LB users

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions