You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, there are pages and components in the same folder called components, it's not easy to navigate by a pogrammer.
Describe the solution you'd like
/src/components/ (components folder)
/src/pages/ (pages folders)
The text was updated successfully, but these errors were encountered:
Quick question about this - does this mean for something like /src/components/CalendarPage you want it split into /src/page/CalendarPage/index.js and the modal components in the components folder?
it sounds like you want
/pages to be a place for actual routing && /components to be components that can be used within those pages.
this can help with confusion of where is the page implemented and where is what it's built out of.
is this going to mess things up for everyone else's branch at this point?
that's a good question - there'll probably be a fair amount of merge conflicts. @Caryyon@paul-rinaldi is this a change we want to introduce while others are working on other branches?
Is your feature request related to a problem? Please describe.
Currently, there are pages and components in the same folder called components, it's not easy to navigate by a pogrammer.
Describe the solution you'd like
/src/components/ (components folder)
/src/pages/ (pages folders)
The text was updated successfully, but these errors were encountered: