Structural twin: assert the "Repeat each depth" checkbox of the thread Passes tab

Open Beginner friendly
#1,848 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
testing

Research direction

Open crates/ui/src/egui_app/tests/structural.rs and find how existing structural assertions check a widget's AccessKit label, role and enabled state; mirror that pattern for the "Repeat each depth" checkbox added to the thread Passes tab by PR #518, and read AGENTS.md for the convention that UI changes update these assertions. Locate the checkbox in the Passes tab UI source to confirm its label and default enabled state, then add the assertion and run the default test suite (cargo test) to confirm it passes. Done means the test asserts label, role and enabled state and passes in the default suite.

Written by the indexing model from the issue text.

Description

area:turning area:ui effort:low P7 source:agent

What is missing: no assertion in the structural twin covers the "Repeat each depth" checkbox that PR #518 adds to the thread Passes tab.

Evidence: crates/ui/src/egui_app/tests/structural.rs has no AccessKit label or enabled-state check for this checkbox. AGENTS.md says that a UI change updates the structural assertions.

Found in the review of PR #518.

Done means: structural.rs asserts the label, the role and the enabled state of the checkbox. The test passes in the default suite.

Dominant language
Rust
Stars
8
Forks
11
Avg merge
6h 45m
Merged PRs (30d)
905

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 NeoTech/Camcraft

All issues in NeoTech/Camcraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.