unyt-org/datex

Refactor visibility across whole project

Open

#771 opened on Apr 27, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Rust (2 forks)github user discovery
enhancementgood first issuenon-blockingtodo

Repository metrics

Stars
 (14 stars)
PR merge metrics
 (Avg merge 53d 4h) (6 merged PRs in 30d)

Description

  1. Make everything invisible, that is not used outside a module (including struct fields), add potential getters if only ro access required
  2. Prefer pub super for module based visibility, if read only access is not required from outside

Contributor guide

Research direction
Identify items that are publicly exposed but not used outside their module, then change their visibility to private or pub(super) as appropriate. Add getters if read only access is needed.
Tech stack
rust
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Rustmodule visibility concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40