algoan-archive / yelloan-tslint Goto Github PK
View Code? Open in Web Editor NEWYelloan TSLinter for backend applications
Home Page: https://www.yelloan.com
Yelloan TSLinter for backend applications
Home Page: https://www.yelloan.com
Warning: The 'promise-function-async' rule requires type information.
Warning: The 'await-promise' rule requires type information.
Warning: The 'no-floating-promises' rule requires type information.
Warning: The 'no-for-in-array' rule requires type information.
Warning: The 'no-inferred-empty-object-type' rule requires type information.
Warning: The 'no-unbound-method' rule requires type information.
Warning: The 'no-unsafe-any' rule requires type information.
Warning: The 'no-unused-variable' rule requires type information.
Warning: The 'no-void-expression' rule requires type information.
Warning: The 'restrict-plus-operands' rule requires type information.
Warning: The 'strict-boolean-expressions' rule requires type information.
Warning: The 'strict-type-predicates' rule requires type information.
Warning: The 'use-default-type-parameter' rule requires type information.
Warning: The 'prefer-readonly' rule requires type information.
Warning: The 'completed-docs' rule requires type information.
Warning: The 'match-default-export-name' rule requires type information.
Warning: The 'no-boolean-literal-compare' rule requires type information.
Warning: The 'no-unnecessary-qualifier' rule requires type information.
Warning: The 'return-undefined' rule requires type information.
Hello,
Since a few days, when you install tslint you are greeted by a warning message saying that TSLint is deprecated.
So we should migrate from TSLint to ESLint. The good thing is that there are some scripts to automatically migrate.
More information on the deprecation: palantir/tslint#4534
Thanks!
Hello,
I have a problem I encountered a few times, so I suggest an update of the rules.
The problem I encounter is with the rule typedef and more precisely the subrule variable-declaration
.
For me we should add the rule variable-declaration-ignore-function
since the rules arrow-call-signature
and call-signature
already enforce the type definition of the functions.
With the variable-declaration
only, we often have typings like this:
const getApplication: (applicationId: string) => Promise<IApplication> = async (applicationId: string): Promise<IApplication> => {};
As you can see, the function signature is typed twice. This double typings is an overhead and can induce an error when refactoring. For instance I often rename the variable declaration typedef and forget to update the function typedef.
While with the variable-declaration
and variable-declaration-ignore-function
, it would look like this:
const getApplication = async (applicationId: string): Promise<IApplication> => {};
What do you think?
Thanks!
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.