search

Ventan00 / quanda

quanda is a service for questions and answers
Apache License 2.0
2 stars 0 forks source link

Components segregation #85

Open Ventan00 opened 3 years ago

Ventan00 commented 3 years ago

We have many components and most of them are only used on one system. How about dividing them into folders according to the system they are used for and put only the shared ones (such as TagSearchBarComponent/PaginationComponent/MessageInputComponent) in the main component folder to make the code more organized?

pnarozniak commented 3 years ago

I agree with you to store single-use components inside folder with name according to system they are used in. But i think we should store reusable components inside "shared" folder. And i would also suggest removing "Component" postfix from components name (it makes their name too long, furthermore they are components by default so i think it is unnecessary)

And what do you guys think about dividing pages into folders as well, where the folder name will be part of page path for example (convention used in next.js framework):

authentication/

login (@page "authentication/login") login (@page "authentication/register") ...

profile/

edit (@page="profile/edit") ...

/

home (@page="/home") ...

Patrykoss commented 3 years ago

I like idea of dividing components to folders based on page which is used for. And after that we can consider removing postfix "Component" in some of them.

Ventan00 commented 3 years ago

Ok, Let's do that