Project architecture: Separate "backend" and "frontend"

[fefzdev]

We currently have all sides of the app at the same level of architecture. The views of the app are mixed up with the Electron backend logic and there is no clear boundaries to separate them.
I'm not sure that create frontend/ and backend/ folders is a good solution but I think we should think about a better way to organise our app.

Pros:

• More logical folder architecture
• Separate app services

Cons:

• Might need to refactor

[MatthieuTD]

It's a good idea, it will allow you to review part of the app to know if everything is in the right place (refracto)

[fefzdev]

Agreed! We should separate Electron logic from the reste of the app

[LahaxeHugo]

It might be a lot of work but it while be easier to expand in the future.

[fefzdev]

Yup it will need a dedicated ticket imo. The app isn't that big for now so the sooner we tackle this the easier it will be

[fefzdev]

I'm not sure about how we could organize it 🤔 I'm open to suggestions

[fefzdev]

src/
├─ backend/
├─ frontend/

isn't a good answer imo

[fefzdev]

I'm using this to generate the tree btw
https://ascii-tree-generator.com/

[fefzdev]

I'm wondering that maybe the issue is just the naming and pattern of the services/ folder. Files in it are closest to APIs talking with the terminal and OS folders than services. Moreover, the services/ folder is kind of the only folder which be designed as "backend"

api/
├─ gitReader/
│  ├─ __tests__/
│  ├─ index.js
├─ folderReader/
│  ├─ __tests__/
│  ├─ index.js
├─ index.js

With a folder structure like this we could add other utils folders like constants or helpers in its root or even more specific ones in each API "services".

api/
├─ utils/
│  ├─ constants/
│  ├─ helpers/
├─ gitReader/
├─ folderReader/
│  ├─ constants/
│  ├─ helpers/
│  ...
├─ index.js

I'm also of the opinion of dropping the class structure in these files since we are only using it there and I find it a bit verbose for no reason.
RFC