open-telemetry / open-telemetry/weaver
Weaver should resolve full URL
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 486
- Forks
- 108
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 40
Description
We use absolute paths in semconv, e.g. docs/database/database-spans.md#sanitization-of-dbquerytext, but it's not quite useful outside of semconv repo. We should resolve full url - https://github.com/open-telemetry/semantic-conventions/blob/v1.34.0/docs/database/database-spans.md#sanitization-of-dbquerytext
Originally posted by @trask in https://github.com/open-telemetry/semantic-conventions-java/pull/217#discussion_r2096797854
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Weaver entry point that resolves absolute links in semantic-convention documentation. Check how the semconv path and version are available, then verify generated links use the full GitHub URL with the repository version and anchor. Done means links like the documented database-spans example resolve outside the semconv repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100