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

Deprecate `resource.render_blocking_status`

Open
  • Is something wrong?
#198 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
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start with model/attributes/resource/resource__render_blocking_status.json and review the linked SDK context to determine the intended replacement for resource.render_blocking_status. Confirm the replacement name and all affected convention references before making changes; done means the old convention is deprecated and the SDK rename is consistently documented.

Written by the indexing model from the issue text.

Description

Good First Issue Task

@abhi said:

Related, I’m going to deprecate https://github.com/getsentry/sentry-conventions/blob/main/model/attributes/resource/resource__render_blocking_status.json because I think we should reserve the resource.X namespace to OTEL resource attributes. We can just rename resource.render_blocking_status in the SDK.

https://github.com/getsentry/sentry-conventions/blob/main/model/attributes/resource/resource__render_blocking_status.json|resource__render_blocking_status.json

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.