hackforla / hackforla/311-data

Epic: Prettier Code Formatting

Open
#1,877 4 comments 0 reactions 0 assignees View on GitHub
Complexity: Small Dependency Epic Feature: automations Feature: Code Health Role: Frontend size: 0.25pt
Dominant language
JavaScript
Stars
73
Forks
74
PR merge metrics
No merged PRs in 30d

Description

### Dependency
- [ ] We will wait until launch before moving on this, as this will disrupt repo-based automations and we don't want to add complexity to our automations until after launch

### Overview

We need to improve code health by adopting and enforcing code formatting rules.

### Tickets

- [x] https://github.com/hackforla/311-data/issues/1872
- [ ] https://github.com/hackforla/311-data/issues/1887
- consider finding an existing open source project with well-documented code formatting rules that would work well with our codebase
- [ ] Implement pre-commit hook to run Prettier on staged files
- [ ] Document Prettier configuration in the wiki, contributing files, and Readme.

### Wiki Pages
- [DR: Implement Prettier Configurations to Standardize Code Formatting](https://github.com/hackforla/311-data/wiki/DR:-Implement-Prettier-configurations-to-standardize-code-formatting)

### Resources
- [comment on ER suggesting using a Pre-commit hook](https://github.com/hackforla/311-data/issues/1872#issuecomment-2524028662)

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.