Get the endpoints toolkit calls by raw path into @sentry/api

Open
#1,879 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
openapi, typescript
Domain
api, cli, tooling

Research direction

Start with the unify-sentry-api-layer task 8.8 and inspect raw-path call sites in cli/src/lib/api/ and mcp-core/src/api-client/. Build an inventory of the endpoints and check which are represented in the Sentry OpenAPI schema. Done means the inventory is checked in, with every endpoint either generated and used or accompanied by a recorded reason for staying raw.

Written by the indexing model from the issue text.

Description

api

Part of #1357. Plan: unify-sentry-api-layer task 8.8 (tasks).

Why

Commands, and through them the MCP (sentry api, sentry schema), can only reach what @sentry/api covers. A path grep finds about 85 raw-path call sites in cli/src/lib/api/ and 55 in mcp-core/src/api-client/, many of them duplicates.

Scope

  • Check in an inventory of every endpoint called by raw path rather than a generated operation.
  • For each: publish it in getsentry/sentry's OpenAPI schema so it generates, or record why it stays raw.
  • Switch call sites to each new operation as it lands.

Related: #1145, #1853.

Done when

  • The inventory is checked in, and every entry is either generated and used, or has a recorded reason.

via @BYK.

--

View Session in Sentry

Dominant language
TypeScript
Stars
961
Forks
179
Avg merge
15h 33m
Merged PRs (30d)
476

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/toolkit

All issues in getsentry/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.