Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Clean up schemas and type definitions

Open
#512 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #527 by @Lms24 — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Compare the definitions in /schemas, docs/src/content.config.ts, and scripts/types.ts, including how the code generation script consumes its types. Decide whether one definition can serve all three uses or how synchronization should work; done means the current divergence risk is addressed across these locations.

Written by the indexing model from the issue text.

Description

Improvement javascript

Seems like we have three type/schema definitions at the moment:

  • /schemas with JSON schema
  • /docs/src/content.config.ts for the Astro docs using astro/zod for validation
  • /scripts/types.ts for the code generation script

It would be nice if we could unify these or at least keep them better in sync. Definitely opens up room for divergence at the moment.
If we could use zod for code generation we can likely eliminate some type casts.

h/t @nsdeschenes for raising!

Dominant language
TypeScript
Stars
16
Forks
7
Avg merge
2d 9h
Merged PRs (30d)
63

Getting set up

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/sentry-conventions

All issues in getsentry/sentry-conventions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.