It would be great if all of these projects included a devcontainer dir & docker file so that they can be run without any machine setup or config

As you may have read in this blog post, we plan to deprecate TSLint in 2019 and support the migration to ESLint as the standard linter for both TypeScript & JavaScript. This will not be an immediate deprecation; on the contrary, there is a lot of work to do to ensure a smooth transition to the new tooling without any regressions. There are

Hello,

I would love to see some instructions on how to get this generated file/folder structure skeleton to work well with google/clasp's set up, specifically where to place its .clasp.json, appsscript.json, etc, relative to the src folder of typescript-library-starter, so that clasp push would work perfectly.

TIA, and good work!

The docs pages for the rules should mention each rule's default.

Otherwise the only way to know is to inspect the code.

• I'm submitting a ...
  [x] feature request

• Summary

tslint has a language service plugin so that tslint runs within the language service and shows linter failures in your editor as red squiggly underlines, the same as type errors.

https://www.npmjs.com/package/tslint-language-service

I'll make a PR at some point; just logging here for the time being.

I want to request a feature.

Typescript noUnusedParameters option ignores params beginning with underscore (understand that some people dislike this, but this is how it is). For such params that are being ignored it would seem preferable to use the optional parameter syntax over providing an unused default value. A default value makes it LESS clear that the parameter is actually not used.

Similar to palantir/tslint#4534... note that all formatting rule requests will be declined because we recommend using Prettier for code formatting.

You may also use this thread as a place to submit feedback about the state of eslint-plugin-react w/ TypeScript.

Update (June 2019): a more concrete roadmap timeline:

• August 1st, 2019: Stop accepting new

🚀 Feature Request

Handle tslint-eslint-rules when converting to directly put them in the `r

• tslint Version: 5.18.0
• typescript Version: 3.5.3

TSLint is completely quiet on file stored in directory starting with number.
I have such tree :

• sources
  • 60m
    • index.ts
  • server.ts

Errors in server.ts are properly highlighted whereas those in index.ts are not shown.

I think the current logo looks fine (font-wise), but the colors/gradient looks off to me (prob cause I suck at gfx). Could be improved.

The README badge would need to be updated with any color changes as well:

What is the best configuration or more strict configuration of rxjs-tslint-rules?

        "rxjs-add": true,
        "rxjs-ban-observables": true,
        "rxjs-ban-operators": true,
        "rxjs-deep-operators": true,
        "rxjs-no-create": true,
        "rxjs-no-unsafe-catch": true,
        "rxjs-no-unsafe-first": true,
        "rxjs-no-unsafe-switchmap": true,
        "rxjs

I'm not sure if this issue is more related to VSCode, tslint or this plugin, but considering that tslint works as expected except for the prettier part I'm starting by posting an issue here.

My project folder structure looks similar to this:

<root>
├── backend
└── frontend
    ├── tslint.js
    └── .prettierrc

In VSCode, I open the project root. Now prettier won't do anyth

Prettier's printWidth defaults to 80, which (if left unchanged) makes TSLint's max-line-length look broken. The reality is that users should be using Prettier options to control the maximum line length.

To ease the pain, this package could probably translate TSLint's max-line-length into Prettier's printWidth automatically when printWidth is not explicitly defined.

We could also wa

Currently only React.forwardRef and React.memo are supported. If using Mobx-React, the observer HOC triggers this error and requires overrides in the file. It would be good if we could add observer to the allowed list.

Perhaps just for the model and handler responses. Or does anyone know of such a tool that works well with serverless?

Is there currently a way to specify the naming convention of a instance property that is assigned a function?

example

class Blah {
// need underscore
    private _testVat = 0;
// don't want underscore
    private test = (): void => { };
}

In TypeScript 2.9, external module can reference to other JSON module. TSLint language service should allow us to ignore JSON files just like TypeScript definition files. I try to exclude JSON file in tslint/typescript config. But it doesn't work.

The following code can fix this issue on VS2017.
fig.ignoreDefinitionFiles === true && fileName.endsWith('.json')) { return prior; }