Skip to content

Conversation

dummdidumm
Copy link
Member

The idea was to be conservative about it, but this causes problems for people not wanting strict type checking but only a basic form of it. Falling back to any is the more pragmatic choice

#2556

@jasonlyu123 any reservations against this?

The idea was to be conservative about it, but this causes problems for people not wanting strict type checking but only a basic form of it. Falling back to `any` is the more pragmatic choice

#2556
@jasonlyu123
Copy link
Member

Ok with fallback to any. There seem to be many more people who got confused about it since the stable release is out 😅. We'll lose the ability to warn people who forgot to type the props. But at least for me that doesn't happen very often.

@dummdidumm dummdidumm merged commit 77160ff into master Nov 12, 2024
3 checks passed
@dummdidumm dummdidumm deleted the any-instead-of-unknown branch November 12, 2024 10:48
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