Add a custom rule to prevent colors from being hardcoded outside of theme (#288)

* Add a custom rule to prevent colors from being hardcoded in ESLint

* Refactor colors

* Create packages folder and fix colors

* Remove external dependency for css alphabetical order linting

* Fix install with yarn

---------

Co-authored-by: Charles Bochet <charles@twenty.com>
This commit is contained in:
Félix Malfait
2023-06-14 16:56:29 +02:00
committed by GitHub
parent bf6fb0ba70
commit 31f3950439
61 changed files with 31490 additions and 62652 deletions

View File

@ -88,16 +88,16 @@ Most default value should work out of the box, but don't forget to update the da
On the frontend:
```
cd front
npm install
yarn
```
On the server side:
```
cd server
npm install
npm run prisma:migrate
yarn
yarn prisma:migrate
```
You can also add `npm run prisma:seed` to seed the database with mock data.
You can also add `yarn prisma:seed` to seed the database with mock data.
### 5. Auth Setup
Right now the only way to authenticate yourself is to setup Google Sign-in in `server/.env`
@ -107,10 +107,10 @@ We will add an easier option soon.
On the frontend:
```
cd front
npm run start
yarn start
```
On the server side:
```
cd server
npm run start
yarn start
```