Remove deprecated APIs in the next major

Aberta
  • Algo errado?
#6,969 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Refatoração
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
react-native, typescript
Domínio
api, developer-experience

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
1.8k
Forks
373
Merge médio
1d 6h
PRs com merge (30d)
103

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de getsentry/sentry-react-native

Todas as issues de getsentry/sentry-react-native

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.