Replies: 4 comments 4 replies
-
|
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) |
Beta Was this translation helpful? Give feedback.
-
|
It might be a lot of work but it while be easier to expand in the future. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure about how we could organize it 🤔 I'm open to suggestions |
Beta Was this translation helpful? Give feedback.
-
|
I'm wondering that maybe the issue is just the naming and pattern of the 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". 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. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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/andbackend/folders is a good solution but I think we should think about a better way to organise our app.Pros:
Cons:
Beta Was this translation helpful? Give feedback.
All reactions