google/comprehensive-rust

Make it easy to react to `dprint fmt` errors

Open

#1,163 opened on Sep 4, 2023

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Rust (2,009 forks)batch import
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (32,954 stars)
PR merge metrics
 (Avg merge 9d 23h) (36 merged PRs in 30d)

Description

We should fix https://github.com/dprint/check/issues/11, which is about making it easy to react to dprint fmt errors.

In short, we should ensure that the errors show up in GitHub on the relevant line in code reviews. Ideally, this should be in the form of a GitHub suggestion.

Contributor guide

Research direction
Explore how to integrate dprint results as GitHub PR suggestions using the Checks API or similar.
Tech stack
rust
Domain
developer experienceci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
Clear
Prerequisites
GitRustGitHub PR review process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60