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

remove @typescript-eslint/no-unsafe-call #1697

Merged
merged 7 commits into from
Oct 8, 2024
Merged

Conversation

chappelo
Copy link
Contributor

@chappelo chappelo commented Oct 5, 2024

All Submissions:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Have you written unit tests?
  • Have you written unit tests that cover the negative cases (i.e.: if bad data is submitted, does the library respond properly)?
  • This PR is associated with an existing issue?

Closing issues

contributes to #1165 by removing @typescript-eslint/no-unsafe-call

note: had to assert RegisterRoutes in the test/*/server.ts files because seems like when routes.ts regenerates, RegisterRoutes would default briefly to any and linting would fail.

@WoH
Copy link
Collaborator

WoH commented Oct 8, 2024

LGTM, thanks so much!

@WoH WoH merged commit 264be8d into lukeautry:master Oct 8, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants