fix: fall back to `any` instead of `unknown` for untyped `$props` #2582

dummdidumm · 2024-11-12T09:00:07Z

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 · 2024-11-12T10:11:10Z

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.

fix: fall back to any instead of unknown for untyped $props

c9faa57

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

dummdidumm merged commit 77160ff into master Nov 12, 2024
3 checks passed

dummdidumm deleted the any-instead-of-unknown branch November 12, 2024 10:48

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: fall back to `any` instead of `unknown` for untyped `$props` #2582

fix: fall back to `any` instead of `unknown` for untyped `$props` #2582

dummdidumm commented Nov 12, 2024

jasonlyu123 commented Nov 12, 2024

fix: fall back to any instead of unknown for untyped $props #2582

fix: fall back to any instead of unknown for untyped $props #2582

Conversation

dummdidumm commented Nov 12, 2024

jasonlyu123 commented Nov 12, 2024

fix: fall back to `any` instead of `unknown` for untyped `$props` #2582

fix: fall back to `any` instead of `unknown` for untyped `$props` #2582