Investigate how editor extensions support Prettier forks
Open
Nobody has claimed this yet.
type:editor support
- Dominant language
- JavaScript
- Stars
- 52.3k
- Forks
- 5k
- Avg merge
- 19h 2m
- Merged PRs (30d)
- 117
Description
(One downside of forking is that it’s not enough to fork just the prettier/prettier repo. You also need editor extensions. And if your team isn’t all using the same editor, or if your project is open source, you are going to need several editor integrations.)
Originally posted by @lydell in https://github.com/prettier/prettier/issues/3101#issuecomment-606764384
Contributor guide
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 with the issue's linked discussion from prettier/prettier#3101 and investigate the editor extensions needed when using a Prettier fork. No files or tests are named; done would mean documenting which integrations support forks and defining the scope of the required work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100