functions with destructuring parameters are not inferred as type predicate correctly

🔎 Search Terms

infer type predicate, destructuring

🕗 Version & Regression Information

• This changed between versions 5.5
• This changed in commit or PR _______
• This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
• I was unable to test this on prior versions because _______

⏯ Playground Link

https://www.typescriptlang.org/play/?#code/C4TwDgpgBAGlC8UDeVSQFxQOQEEsG4oBDTAZ2ACcBLAOwHMoBfKAH2VXAkywCECoARmUq0GjfACgANhGBQAHqUwwA2gF0EUdZIkB6XVFIALAPYBXKQBMoNE3IgUKJihIDGJmuSgAzKlOAOEJYAjJgoaFzYeIQkhiL0TOqaihJQUAB0vv4OABQ54ZxMAJQIAHwckAjwiLhYRTrunnJZARRBAExhFZG1McLUCYxJiClpmX6tOfJlCukRVTV49RJAA

💻 Code

type X = { type: 'A'; a: string } | { type: 'B'; b: string };
let xs: X[] = [];

// should not error
const filtered1: { type: 'A'; a: string }[] = xs
  .filter(({ type }) => type === 'A');

const filtered2: { type: 'A'; a: string }[] = xs
  .filter(x => x.type === 'A');

🙁 Actual behavior

error on filtered1

🙂 Expected behavior

not error on filtered1

Additional information about the issue

No response

Inizia con la riproduzione collegata in TypeScript Playground e confronta il callback con parametro destrutturato con il callback con parametro diretto. Traccia l'inferenza dei predicati di tipo per i callback di filter e verifica il completamento quando filtered1 accetta il tipo di array ristretto senza errori.