I'm using visual studio code for a typescript project, where I use some 3rd party npm js libraries. Some of them don't provide any ts types (types.d.ts file), so whenever I use parameters or variables without specifying their type, vs code's linting shows this error: parameter implicitly has an 'any' type. Also, ts wouldn't compile.
How can I prevent this from happening?
You are using the --noImplicitAny and TypeScript doesn't know about the type of the Users object. In this case, you need to explicitly define the user type.
Change this line:
let user = Users.find(user => user.id === query);
to this:
let user = Users.find((user: any) => user.id === query);
// use "any" or some other interface to type this argument
Or define the type of your Users object:
//...
interface User {
id: number;
name: string;
aliases: string[];
occupation: string;
gender: string;
height: {ft: number; in: number;}
hair: string;
eyes: string;
powers: string[]
}
//...
const Users = <User[]>require('../data');
//...
This answer was mostly copied/inspired by Vitalii's answer, but since it had to be modified a bit, to work with my project, I am also adding this answer.
On top of each file where I use external code, I added:
if (undefined) var { -List of Namespaces used- } = require("./globals");
Undefined is the shortest and simplest way (that I thought of) of having a constant false value without triggering eslint or jshint. This ensures that the code will never be run, while still "requiring" the jsdoc.
I used var instead of let or const since it will not stay in the if scope, but rather the global file scope.
This will actually declare the variables inside the {} (as undefined), but typeof undeclared and typeof undefined are both "undefined", thus there is no difference in the code.
By having all the declarations in one file, I can get all the namespaces by destructuring one require statement in one line.
But keep in mind, that in order for this to work, you need to be using export and not declare in your typings file.
I cannot view the interfaces in globals.d.ts from JavaScript files.
export namespace Namespace {
export interface Interface {
property: string;
}
}
I have temporarily fixed this problem by renaming the namespace with the interfaces to Interfaces (also fixed all the references in globals.d.ts) and created another Namespace with constants that implement the interfaces, like so:
export namespace Interfaces {
export interface Interface {
property: string;
}
}
export namespace Namespace {
export const Interface: Interfaces.Interface;
}
I also had trouble using the namespaces from globals.d.ts in JavaScript comments. To solve this problem I added typeof infront of the type, like so: /** @param {typeof Namespace.Interface} */
I have now found a way to export interfaces from .d.ts files to .js files, you can find the answer here.
In typeScript you should install @types/react and while extending the React.Component you need to specify the props and state types.
Here is the example
import * as React from 'react'
interface Props {
... // your props validation
}
interface State {
... // state types
}
class FormExample extends React.Component<Props, State> {... }
In the meantime (after hours of struggling) I came across my own solution.
Simply set the compiler option allowJs to true in tsconfig.json and save.
{
"compilerOptions": {
"target": "ES5",
"module": "commonjs",
"allowJs": true
}
}
This is obviously a bug because it´s default is true according to the docs. I´ve posted this issue additionally on github.
First, to make typescript tolerate parameters without declaring their type, edit the
tsconfig.jsonSecond, install the tslint npm package as a prerequisite for the tslint vs code extension
Third, install the tslint vs code extension