hackforla / hackforla/311-data

DEV - Implement Prettier code formatting standard

Open
#1,887 13 comments 1 reaction 0 assignees View on GitHub
Complexity: Medium Feature: Code Health ready for dev lead Role: Frontend size: 0.25pt
Dominant language
JavaScript
Stars
73
Forks
74
PR merge metrics
No merged PRs in 30d

Description

### Dependency
- [x] ~We don't want any devs to pick this up until after we have launched. Completing this ticket will require all devs to pause work on tickets until they have adopted Prettier. Dev lead expects to manage bugs that come up while devs are integrating Prettier~
- https://github.com/hackforla/311-data/issues/1865

### Overview

Propose formatting standard for the 311 Data repo with Prettier

### More Info (optional)

Consider finding an existing open source project with well-documented code formatting rules that would work well with our codebase

### Action Items

- [ ] Developers install the Prettier extension in VSCode. [Prettier-VSCode repo](https://github.com/prettier/prettier-vscode)
- Refer to the Readme to install Prettier.
- [ ] Once installed, we'll discuss any bugs we come across on our local repo.
- [ ] Fix any issues that come up.
- [ ] Push a PROD ready branch to 311-data/main.
- [ ] Propose a code formatting standard. Consider providing...
- `.prettierrc`
- `.editorconfig`
- examples of this formatting configuration on another repo
- [ ] Team demo, get feedback
- [ ] Push Prettier team standards config to 311-data/main branch.

### Resources/Instructions

- Link to @efrenmarin45 Dev.to article on Prettier: https://dev.to/efrenmarin/format-your-code-using-prettier-like-a-pro-fj8

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.