ts-reset

ts-reset copied to clipboard

#182 I'll change the tests if you think this is worth merging

Flammae

Currently calling the filter(Boolean) method on a tuple turns it into an array of union: ```ts let tuple = ["foo", undefined, "bar", 0] as const; tuple.filter(Boolean) // ("foo" | "bar")[]...

Flammae

fix: JSON.parse accepting null

4

Please let me know if I missed anything in this. Fixes: https://github.com/total-typescript/ts-reset/issues/173

ImLunaHey

custom filter callback not inferred when rule applied

2

Hi, ```ts // you need to save/refresh page in playground to get rid of effect after (un)comment // import '@total-typescript/ts-reset'; const isPropTruthy = (propName: K) => { return (item: T):...

ssukienn

Typesafe `new Array().fill()`

3

`new Array()` returns `any[]`, so filling it with given value doesn't narrow the array type. Maybe this could be improved here.  https://www.typescriptlang.org/play?#code/MYewdgzgLgBAhgJwTAvDMBTA7jAgkuATwAoBGABgEoA6AMwEsAbR4qgWACgB6LmPmAHoB+IA

thetarnav

Better typings for KeyboardEvent.key

3

KeyboardEvent.key is typed as a string, even though it's a union of string literals. ```tsx window.addEventListener('keydown', (e)=>{ // string type e.key }) ``` Would be really nice to get autocomplete...

iway1

Add monorepo instructions to the README

5

Just setup ts-reset for my monorepo and found this was the most painless way to do it, updated the README to reflect how I set this up for my monorepo,...

RhysSullivan

Added improved typings for Array.every

2

This PR adds improved typings to `Array.every` when using the `Boolean` constructor, in a way that's very similar to what's already being done for `Array.filter`. After extensive testing, these types...

feathecutie

Would anyone else find it useful to add the string type to the number passed to a NumberFormat.format call? I've been using this with a decimal math library, and am...

pc-erin

Narrow types for certain cases of Array.includes

2

As discussed in #49 a simple `: searchElement is T` won't do, because the assertion is too strong and produces wrong types, especially in the "opposite" cases (e.g. else blocks)....

schummar