You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2022. It is now read-only.
We should compare the types of what is exported in the declaration file against the inferred types of what is exported in the JS source. This most likely should be used to provide warnings/suggestions, because JS type inference might not be good enough for this to be used as a lint rule. The implementation should also be resilient enough to avoid emitting useless information when inference of JS types doesn't work well.
Example:
js
module.exports.str="clearly a string";// Inferred type: "string"
d.ts
exportconststr: number;// Wrong type
In this case we'd want a warning that the type of str could be wrong.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should compare the types of what is exported in the declaration file against the inferred types of what is exported in the JS source. This most likely should be used to provide warnings/suggestions, because JS type inference might not be good enough for this to be used as a lint rule. The implementation should also be resilient enough to avoid emitting useless information when inference of JS types doesn't work well.
Example:
js
d.ts
In this case we'd want a warning that the type of
str
could be wrong.The text was updated successfully, but these errors were encountered: