RFC: support for deno fmt
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 52
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 19
Description
Problem
Much in the same way the deno-lint bindings provide value, so too could deno-fmt bindings.
Discussion
- Are there inhibitors to replicating what was done for lint for fmt?
- Are there reasons not to include such functionality?
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the existing deno-lint bindings, which the issue identifies as the reference point for deno-fmt support. Determine whether the same approach is suitable and resolve the listed questions about inhibitors and reasons not to include the functionality; the RFC is done when those questions have a decided implementation direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, nodejs, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100