---
# System prepended metadata

title: Frontend Style Guide

---

### [⬅ Return Home](https://hackmd.io/@AAK-TELECIENCE-FRONT/home)

# Frontend Style Guide

To avoid code format discutions the project applies prettier format on every commit. 

# Commits

We use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/#specification) convention and to enforce that, every programmer should create commits using the VSCode extension 
```
vivaxy.vscode-conventional-commits
```

# Branch names

Based on conventional commits we will use the format

```
<feat|fix|etc>/<branch-name>
```

Example:

```
fix/resolving-some-weird-issue
```

# Package Manager
- Never use `npm`, it produce weird issues
- Always use `yarn`

# Pull Request


### A pull request description must contain:

- [ ]  The ticket's name
- [ ]  A screenshot of the changed section if there is a UI change
- [ ]  Any aditional comments that let your partners to understand your decisions
- [ ]  Copy the ticket on the PR description

### Merge

To merge a pull request you must have:
- [ ]  The approve of the Team Lead
- [ ]  At least one more approval of another Frontend Team member

### Story Points



| Time sandbox | Story Points |
| -------- | -------- |
| one hour     | 1     |
| half day (4 hours)     | 2     |
| full day (8 hours)     | 3     |
| three days     | 5     |
| one week     | 8     |
| need to split the task     | 13     |

### [⬅ Return Home](https://hackmd.io/@AAK-TELECIENCE-FRONT/home)
