explain why type argument was removed

pull/10694/head
Rich Harris 2 years ago
parent 01c67a0407
commit c19754c3f3

@ -473,6 +473,15 @@ type MyProps = any;
let { a, b, c, ...everythingElse }: MyProps = $props(); let { a, b, c, ...everythingElse }: MyProps = $props();
``` ```
> In an earlier preview, `$props()` took a type argument. This caused bugs, since in a case like this...
>
> ```ts
> // @errors: 2558
> let { x = 42 } = $props<{ x: string }>();
> ```
>
> ...TypeScript [widens the type](https://www.typescriptlang.org/play?#code/CYUwxgNghgTiAEAzArgOzAFwJYHtXwBIAHGHIgZwB4AVeAXnilQE8A+ACgEoAueagbgBQgiCAzwA3vAAe9eABYATPAC+c4qQqUp03uQwwsqAOaqOnIfCsB6a-AB6AfiA) of `x` to be `string | number`, instead of erroring.
Props cannot be mutated, unless the parent component uses `bind:`. During development, attempts to mutate props will result in an error. Props cannot be mutated, unless the parent component uses `bind:`. During development, attempts to mutate props will result in an error.
### What this replaces ### What this replaces

Loading…
Cancel
Save