Repository lacks style guidelines
Open
enhancement
- Dominant language
- TypeScript
- Stars
- 91
- Forks
- 65
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 1
Description
Prettier options would better help maintain preferred style standards. I do not mind driving this but would like some feedback on what is important to team.
Contributor guide
Research direction
No files or tests are named. Start by reviewing the repository's current formatting setup and the issue's request for Prettier options, then seek the team's feedback on preferred standards. Done means the style guidelines and agreed formatting configuration are documented or established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation, tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100