Write a codefmt FAQ

Open Beginner friendly
#53 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
vim
Domain
documentation

Research direction

Review README.md and the existing FAQ content in the Formatter Integration Guide, including the linked question about why to use codefmt instead of formatprg. Consolidate the relevant answers into a main FAQ in the README, with the FAQ covering the questions users are likely to have.

Written by the indexing model from the issue text.

Description

enhancement

Codefmt raises a few questions like why not just use formatprg that we should officially answer in the docs, pbb in README.md.

I added a bit of FAQ content to https://github.com/google/vim-codefmt/wiki/Formatter-Integration-Guide. Part or all of that can be merged into a main FAQ.

Dominant language
Vim Script
Stars
1.1k
Forks
102
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 google/vim-codefmt

All issues in google/vim-codefmt

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.