microsoft / microsoft/TypeScript

[7.0 regression] Type parameter default is ignored when the call sits inside a callback passed to a generic function

Aperta
#63,949 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

  • #63988 di @copilot-swe-agent — chiusa senza merge
Bug
Lingua principale
Go
Stelle
111k
Fork
14.3k
Merge medio
2g 4h
PR unite (30g)
132

Descrizione

🔎 Search Terms

type parameter default
type parameter inference
default type argument
generic default
not assignable to parameter of type 'undefined'
tsgo generic
ts7 generic

🕗 Version & Regression Information
  • This changed between versions 6.0.3 and 7.0.0
⏯ Playground Link

https://www.typescriptlang.org/play/?ts=6.0.3#code/PTAEBUGVQdgOgAxwEygE4FMDmmDOuBLAewDsAuUXABwFc1ibdQAiEogF1AEN8CsSuAIwA2GUOyKgqXNFwC2GdhjSgiAM3EBPKmIDkNEgBMMagiQyHdzALAAoEHZCgAgqCwZz9AMag1Br+zEJKAA7gAWRLhi7Npi0rIKSioABuDJoGE83KAAVMZqXDTC7DncRqAETIwWoIIcYY5gALQVwVxSMvKKylo6oAAUghhhZobZXqSGBIGkXMK9GACUADRlho2gLWYV7Ew5ZmrKmIalmOx0wTE6G8KRGEzsmZz5hcWhYR7iH6Bec-OZVB0JCYZkIxnGf0EXC8AGsvlxOJUdlFhBpHhgNjIsDQFCROOoyvUeu5PAQfH4SAEggMMHAsHBQAAlDDQ9i6KpRADCkOhMMWcEaGygoAAbIg4ABmChsUBHIhoBmgCDQeBIVBgeAARkQTWMADcKHKVKQvmJkoYEVx0licR52ALbHZjF5hDIxBSqSbDuwvB80AAeAAiAD4Bl41FgKAYYWwQiRFhQAApoIhySoYIPBux2K5iRlEGhKXD+xmhgC8TNlAA8lEYmLoq7pQAB+UAAb1AAEkAHIUDsG0AkHFDFQAX1WAHkAKrgCi4dj0EhYUCj0DSjB65TZ+xgbsT8AAUWlkjOFwWZTY7AR1KaLXR6EUZ9zFRBJEOaGOa1AuJmwIgDo9X9qwwLxCwwAAxRRfRLata0MJh50XLBVnAUAK3zMDi1LUN+jsJUUzAihGWWPDaiIQxNGbChUIwGsPHgpkQPlQx-V0HtdFWLgSE0UNW3AABtNju10ABdNdBw3LdbEWdtSNPNBgm9X1lH9Gi6LrRiJjQFjdGncAOLKHiWwgQS9NE8TwGDfoOwIpRVjqCiV0WOxR23Z1XUwXx-CA6puWEYQoVhVTYPophwO8oIcK8QRqNWYwqFwKMSBjIg434kSEwgUAnHuYQzHYXVKiEUQmjy8xt1oqh5U4CZgRqwQ0NAXyeVhfp+gtK8+1AAchzkEcnLQ0M2zkx8FOA0ClEgn0wn6BsDI6rhnNsJUnCVNb1o2zalQAPV27bSKcYUYEND95WVZAJQAFgAVgoZw0GxH9VDRWJQF0ftpWHZQAG4VybJFL24Xh+GKjFluysBNokDoEm6Y0Xr6fQjBMMwLF0B0VrAfoCDgWlQFSdIQiyQGXiKJQxmhjCi1Yxtg1WXBJHvWqpl-OZxCIIg4XRA7IYKYQolqWRKTCTZQ2ScxNzQZJOPKcXJJUAAfJrkdMcxDHSJoxYMfJUfVpbx1AdKlqFb4cjwMnSmfJF5wIfyfnlTAAlaMjHm65RCFIJh+mTVN039RCzCwYMVneMkGh3SgIhCB5viNe2FCYNQUzkbIplwX5tJqA5lA8Lw4h4RK7Eq6r7bqn4PlhJNk79gOl3LH5BGs7qKE1Jy7CAA

💻 Code
// TS 7.0.2 regression: spurious "not assignable to parameter of type 'undefined'"
//
// A generic function whose type parameter `T` has a *default* and is used both
// - in a parameter type (behind a conditional type), and
// - in its *inferred* return type
// loses that default when the call happens inside a callback that is itself the
// argument of another generic function (e.g. React's useCallback).
//
// TS 6.0.3: no error.   TS 7.0.2 / 7.1.0-dev: error on the `data` argument.

declare function fetcher<D> (cfg: unknown): Promise<D>

type Routes<R> = R extends 'x' ? { IN: { v: number }, OUT: string } : never

// NOTE: no return type annotation -- the return type is inferred and mentions T.
function executeFetch<R extends string, T = Routes<R>> (
  route: R,
  body?: T extends Record<'IN', any> ? T['IN'] : never
) {
  return fetcher<T extends Record<'OUT', any> ? T['OUT'] : T>({ route, body })
}

declare function useCallback<T extends Function> (cb: T, deps: unknown[]): T // eslint-disable-line

export const cb = useCallback((data: { v: number }) => {
  return executeFetch('x', data)
  //                       ^^^^
  // TS 7: error TS2345: Argument of type '{ v: number; }' is not assignable
  //       to parameter of type 'undefined'.
  // (i.e. `T` was not defaulted to Routes<'x'>, so the conditional took the
  //  false branch -> `never`, and `never | undefined` -> `undefined`)
}, [])

// The *result* type is still correct in both versions (Promise<string>), which
// shows the error comes from a discarded inference pass:
export const check: Promise<string> = cb({ v: 1 })
🙁 Actual behavior

Error: Argument of type '{ v: number; }' is not assignable to parameter of type 'undefined'.

🙂 Expected behavior

The proper type should be inferred on the function generic

Additional information about the issue

This issue was discovered in a large codebase and Claude Opus 5 was used to identify the issue and construct the reproduction.

It's worth noting that the TypeScript Playground does not support TS7 so this issue needs to be debugged locally (simply run tsc on the code and compare the errors (or lackthereof) between versions 6 and 7)

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia eseguendo la riproduzione fornita con build locali di TypeScript 6 e 7 usando tsc, come raccomandato dall’issue, e confronta le diagnosi. Traccia il comportamento del valore predefinito e dell’inferenza del parametro di tipo generico per executeFetch all’interno di useCallback. Il lavoro è completato quando il callback accetta { v: number } senza errori, mentre cb mantiene il tipo del risultato Promise.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
typescript
Ambito
compilers
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Attiva
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.