consider linking to specific line numbers

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
ci-cd, devtools

Research direction

Start by reproducing the truncated diff output referenced in the linked pull-request comment and inspect how log output is grouped and rendered. Done means omitted sections are clearly separated, each group links to its first relevant log line, and the resulting output makes the source file easy to locate.

Written by the indexing model from the issue text.

Description

I noticed this issue in this comment where the diff output is cut off just one line too early. if each group contained a link to its first line, i could easily navigate to the relevant log line and see what file the diff occured in.

additionally, --- is not a clear indicator for "some output has been omitted here", as --- also is a common part of diffs. more clear would be having each chunk in a separate code block, with line-number links in-between.

Dominant language
Rust
Stars
52
Forks
27
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 rust-lang/rust-log-analyzer

All issues in rust-lang/rust-log-analyzer

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.