rust-lang / rust-lang/rustdoc-types

Consider exposing effective visibilities

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

Nobody has claimed this yet.

Dominant language
Rust
Stars
44
Forks
20
PR merge metrics
No merged PRs in 30d

Description

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.

Research direction

Start with the linked EffectiveVisibilities documentation and inspect rustdoc-types' JSON output definitions to determine how this information could fit the interface. Done requires a maintainer-agreed scope and exposing the effective visibility data in the output, with appropriate coverage if the change is accepted.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.