Skip to content

Conversation

@tstirrat15
Copy link
Contributor

Description

Part of getting this codebase closer to strictly following Typescript's recommendations, which provides better type-safety and ideally better behavior.

The idea behind this one is that if typescript can't infer the type of a function argument, especially in a callback function, it will type it as any. This is the "implicit" any in the rule. This configuration change makes typescript yell at you about it.

I don't think I uncovered any actual bugs here, but it means the guardrails should be better.

Changes

Will annotate.

Testing

Review. See that tests pass.

@vercel
Copy link

vercel bot commented Oct 9, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
playground Ready Ready Preview Comment Oct 17, 2025 7:45pm

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

};

// TODO: this is creating a new `run` on every render. Refactor so that the reference is stable,
// or else use an off-the-shelf debounce.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alecmerdler
alecmerdler previously approved these changes Oct 17, 2025
Copy link

@alecmerdler alecmerdler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome

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.

3 participants