We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In many cases the type can be inferred and adding parens just adds noise
E.g. mypromise.then(data => .... ) is arguably cleaner than mypromise.then((data : IData) => ... )
mypromise.then(data => .... )
mypromise.then((data : IData) => ... )
If we know mypromise is of type IPromise<IData> then we don't need the additional type info in the arrow function
IPromise<IData>
The text was updated successfully, but these errors were encountered:
@hisuwh Is this still an issue? Just tried to replicate and didn't have any luck.
Sorry, something went wrong.
@Jameskmonger This was still presenting due to the comments in the file breaking the linting. Closing this now
No branches or pull requests
In many cases the type can be inferred and adding parens just adds noise
E.g.
mypromise.then(data => .... )
is arguably cleaner thanmypromise.then((data : IData) => ... )
If we know mypromise is of type
IPromise<IData>
then we don't need the additional type info in the arrow functionThe text was updated successfully, but these errors were encountered: