search

ch-a-os / DocSort

Digitize and access everything, everywhere.
GNU General Public License v3.0
0 stars 1 forks source link

Think about file-/folder structure for classes #112

Open ghost opened 5 years ago

ghost commented 5 years ago

We should think about where we put additional classes like in the getAllTags-EP. We create the new class TagCount but we maybe should put such classes into a separate folder. Maybe backend/lib/classes for the backend? Same could be done for the frontend but primary the backend should be focused.

Mondei1 commented 5 years ago

This is a good question. For cases like TagCount I would leave it as it is. Because it get only used in that one file. But for our ConfigManager I would put it into that classes folder or leave it in the lib/ folder.

ghost commented 5 years ago

Maybe we should also move classes to some class-folder, even if it's not used somewhere else (yet). Otherwise, if you want to change a class, you need to think about where it actually is declared^^°.

ghost commented 5 years ago

@Mondei1 I would suggest, we use src/classes/ for the class-objects? Or do you think something like src/lib/classes/ fits better? I would think of src/lib as a folder that's just for functions^^

Mondei1 commented 5 years ago

The lib folder is for everything which is a library (I know I'm genius ^^) that includes classes too. I would create that classes folder in lib.

Sure we can put single used classes in that folder but If the project grows, we search with VSCode anyway where that one class is.