FuelLabs/sway

Organize test suites in `swayfmt`

Open

#2,494 opened on Aug 9, 2022

View on GitHub
 (7 comments) (0 reactions) (1 assignee)Rust (5,421 forks)batch import
ODHack13forcformattergood first issuemay be rewardedtesting

Repository metrics

Stars
 (61,702 stars)
PR merge metrics
 (Avg merge 22h 6m) (16 merged PRs in 30d)

Description

  • parens
  • block
  • array #2593 @eureka-cpu
  • asm
  • return
  • conditionals
    • if/else #2597 & #2564 @eureka-cpu
    • match #2539 & #2530 @eureka-cpu
  • while
  • index
  • tuple field projection
  • ref & deref
  • bitwise operators
  • comparison operators
  • logical operators
  • reassignment
  • #2497

Edit: Extending this to re-organizing all tests in swayfmt

Contributor guide

Research direction
Review the current test structure in swayfmt, identify incomplete test suites from the checklist, and add tests for missing items like 'parens', 'block', 'asm', etc. Use existing test patterns as a reference.
Tech stack
rust
Domain
testing
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70