Giter VIP home page Giter VIP logo

tslint-rules's Introduction

Build Status Coverage Status dependencies dev-dependencies

NPM

tslint-rules

A set of custom TSLint rules.

Usage

Install from npm to your devDependencies:

npm install --save-dev custom-tslint-rules

Configure tslint to use the custom-tslint-rules folder:

Add the following path to the rulesDirectory setting in your tslint.json file:

{
   "rulesDirectory": [
     "node_modules/custom-tslint-rules/dist"
   ],
   "rules": {
     ...
   }
}

Now configure some of the new rules.

Available Rules

import-barrels

Enforces usage of barrels (`index.ts`) when importing from a directory that has a barrel file.

Rationale:

Allows directories that contain multiple modules to be handled as a single module with a single public interface and opaque inner structure.

This rule works only for ES2015 module syntax import statements and checks only relative module paths.

Usage:

"import-barrels": [
  true,
  {"noExplicitBarrels": false, "fileExtensions": ["ts", "js"]}
]

Options:

An argument object may be optionally provided, with the following properties:

  • noExplicitBarrels = false: disallows usage of explicitly named barrels in import statements (import foo from './foo/index')
  • fileExtensions = ['ts', 'js']: uses the provided file extensions for module and barrel file lookup
  • fixWithExplicitBarrelImport: uses the provided string to replace non-barrel imports in --fix mode (i.e. when set to 'index', import foo from './foo/some-module' becomes import foo from './foo/index')

jasmine-no-lambda-expression-callbacks

Disallows usage of ES6-style lambda expressions as callbacks to Jasmine BDD functions.

Rationale:

Lambda expressions don't create lexical this bindings in order for this bindings from outer function scopes to be visible inside of lambda expressions. This beats Jasmine's own system of managing shared state by passing in a dictionary object as this reference to the user-provided callbacks to take over the memory management from the JavaScript VM to prevent memory leaks during test runs.

This rule will also check for cases where a call to a function is made with a lambda expression parameter instead of passing a lambda expression directly as callback to support Angular 2 test style:

beforeEach(async(() => {
  ...
}));

it('something', inject([Service], (service) => {
  ...
}))

Usage:

"jasmine-no-lambda-expression-callbacks": true

Options:

Not configurable.

Contributions and Development

Issue reports and pull requests are highly welcome! Please make sure to provide sensible tests along with your pull request.

To get started with development, clone the project and run npm install. To run the tests execute npm test. npm run cover will run the tests along with generating a coverage report.

tslint-rules's People

Contributors

bendingbender avatar greenkeeper[bot] avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar

tslint-rules's Issues

An in-range update of @types/lodash is breaking the build 🚨

The devDependency @types/lodash was updated from 4.14.121 to 4.14.122.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of rimraf is breaking the build 🚨

The devDependency rimraf was updated from 2.6.3 to 2.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 2 commits.

  • 250ee15 2.7.0
  • dc1682d feat: make it possible to omit glob dependency

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Hi dimi,

Wo würdest du ansetzten wenn du die in @NgModule vorhanden Arrays sortieren wollen würdest?
Ich finde im Walker leider nicht die Richtige Function dafür.

Hast du einen Ansatz?

An in-range update of @types/node is breaking the build 🚨

Version 7.0.26 of @types/node just got published.

Branch Build failing 🚨
Dependency @types/node
Current Version 7.0.25
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
  • coverage/coveralls First build on greenkeeper/@types/node-7.0.26 at 96.774% Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.