How should group_imports handle visibility?
Open
Nobody has claimed this yet.
C-discussion
T-style
UO-group_imports
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
- What should be the default behavior with how imports are grouped by visibility?
- Should
pubitems be sorted differently at all? - Should
pub(<visibility>)be sorted differently thanpub? - Sort by visibility then by name or just by name? What about
pub(in a::b)? - Should
pub(<visibility>)cause more blank-line-separated groups? (e.g. apubgroup and apub(crate)group, etc.) or just one group for allpubitems?
- Should
- What config options should be available?
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
No files, tests, or entry points are named in the issue. First resolve the proposed visibility ordering, grouping, and configuration behavior, then identify the relevant rustfmt implementation and tests; the work is done when the decisions are implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100