Remove deprecated APIs in the next major

Aperta
  • Qualcosa non va?
#6,969 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react-native, typescript
Ambito
api, developer-experience

Direzione di ricerca

Start with the listed entry points: options.ts, client.ts, touchevents.tsx, index.ts, tracing/timetodisplay.tsx, and tracing/integrations/appStart.ts. Remove the deprecated APIs and options identified in the issue, then update the referenced TODOs in test/client.test.ts and test/sdk.test.ts. Check the v8 to v9 migration guide work tracked in #6735; done means the untracked removals and follow-up notes are addressed.

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

Descrizione

React-Native Task

Description

Several APIs and options are still exported after one or more majors, some with JSDoc that says "will be removed in the next major version". Remove them in the next major.

Items that already have their own issue are listed for reference only.

To remove (no dedicated issue)
  • initialScope option (options.ts). Use Sentry.getGlobalScope().setTag(...) / setUser(...) instead.
  • ReactNativeClient.captureUserFeedback (client.ts). Use Sentry.captureFeedback instead. Also update the remaining test TODO in test/client.test.ts.
  • ignoredDisplayNames prop on TouchEventBoundary (touchevents.tsx). Use ignoreNames instead.
  • useThreadsForMessageStack option (options.ts). Use beforeSend instead.
  • bufferSize on ReactNativeTransportOptions (options.ts). Use the root maxQueueSize option instead.
  • instrumentLangGraph re-export (index.ts). Use instrumentStateGraph instead.
  • startTimeToInitialDisplaySpan / startTimeToFullDisplaySpan (tracing/timetodisplay.tsx). Use the <TimeToInitialDisplay> / <TimeToFullDisplay> components instead.
  • Internal captureAppStart (tracing/integrations/appStart.ts). Use Sentry.appLoaded() instead.
Tracked separately
  • #5882: _experiments.replaysSessionSampleRate / replaysOnErrorSampleRate
  • #6681: _experiments.androidProfilingOptions
  • #6680: enableExperimentalViewRenderer
  • #5932: FeedbackWidget* aliases
  • #5896: FeedbackButton, showFeedbackButton, hideFeedbackButton
  • #6143: TTID/TTFD record prop
  • #6001: sendDefaultPii
Follow-up
  • Remove the related // TODO: No longer an experiment on major version. notes in test/sdk.test.ts.
  • Document each removal in the v8 → v9 migration guide (#6735).
  • Consider a check that flags @deprecated APIs older than one major, so this list doesn't build up again.
Lingua principale
TypeScript
Stelle
1.8k
Fork
371
Merge medio
1g 6h
PR unite (30g)
114

Preparare l'ambiente

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.

Altre issue di getsentry/sentry-react-native

Tutte le issue di getsentry/sentry-react-native

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.