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

chore: Add warnings about unsafe use of any #278

Merged
merged 1 commit into from
Oct 25, 2024

Conversation

e-fisher
Copy link
Collaborator

Description

Add warnings about unsafe assignment until we add recommended type checked eslint config and address all the errors to avoid adding more errors in the meantime.

How to Test

Checklist

  • I have performed a self-review of my code.
  • I have added tests for my changes.
  • I have run linter locally (npm run lint) and all checks pass.
  • I have run tests locally (npm test) and all tests pass.
  • I have commented on my code, particularly in hard-to-understand areas.

Screenshots (if appropriate):

Related PR(s)/Issue(s)

@e-fisher e-fisher marked this pull request as ready for review October 25, 2024 08:20
@e-fisher e-fisher requested a review from a team as a code owner October 25, 2024 08:20
@e-fisher e-fisher requested review from going-confetti and cristianoventura and removed request for a team October 25, 2024 08:20
@e-fisher e-fisher merged commit 32cabea into main Oct 25, 2024
2 checks passed
@e-fisher e-fisher deleted the chore/add-warnings-unsafe-any branch October 25, 2024 12:43
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