Build sentry schema's index from the @sentry/api operation catalog

Open
  • Is something wrong?
#1,894 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
54/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
api, cli

Research direction

Read the design and tasks linked in the issue, especially task 4.2, then inspect the sentry schema implementation and @sentry/api/operations. Confirm dependency #1876 is complete before starting. Done means sentry schema reads its index from the operation catalog and its output remains unchanged.

Written by the indexing model from the issue text.

Description

api CLI enhancement

Part of #1357. Plan: cli-first-mcp task 4.2 (design, tasks). Depends on #1876.

sentry schema keeps its own index today. Read it from @sentry/api/operations instead, so it always matches the client.

Done when

  • sentry schema output is unchanged.

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.