Skip to content
New issue

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

False negative with TypeScript rules that don't have type parameters #202

Closed
bmish opened this issue Oct 11, 2021 · 0 comments · Fixed by #209
Closed

False negative with TypeScript rules that don't have type parameters #202

bmish opened this issue Oct 11, 2021 · 0 comments · Fixed by #209

Comments

@bmish
Copy link
Member

bmish commented Oct 11, 2021

note that it's not required that you declare type parameters.

In general - we are lazy and avoid declaring the type arguments if there are no options (example).

If there are no options then TS can infer [] as the options type, and it can infer the messageIds from the object literal definition.

Ideally as well you wouldn't ever need to declare two parameters... but that's a problem with TS (there's no way to tell TS "use this explicit generic and infer the second generic) :(

Originally posted by @bradzacher in #197 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant