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.

Sign up for GitHub

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

Jump to bottom

fix: use 'unknown' instead of 'any' for type Exact #4461

Merged
merged 2 commits into from
Aug 2, 2020
Merged

fix: use 'unknown' instead of 'any' for type Exact #4461

merged 2 commits into from
Aug 2, 2020
+57 −57

Conversation

mjbcopland
Copy link
Contributor

Resolves "Unexpected any. Specify a different type." from @typescript-eslint/no-explicit-any.

Why am I linting generated files?

  1. It's useful when using ESLint as a lifecycle hook.
  2. It's useful to prevent any being used for custom scalar types.

@mjbcopland
fix: type Exact<T> no-explicit-any

Verified

This commit was signed with the committer’s verified signature.
jorgepiloto Jorge Martínez
GPG key ID: FAD7B35818BE79D9
Verified
Learn about vigilant mode
ded88b7
@mjbcopland
chore: update dev-test

Verified

This commit was signed with the committer’s verified signature.
jorgepiloto Jorge Martínez
GPG key ID: FAD7B35818BE79D9
Verified
Learn about vigilant mode
78126db
@dotansimha
Copy link
Owner

Perfect, thank you @mjbcopland !

@dotansimha dotansimha merged commit d2e15aa into dotansimha:master Aug 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@mjbcopland @dotansimha