Project structure #20
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Aidasvenc
requested review from
AlbertoCentonze,
gaspardthrl,
Fyuryy,
GustaveCharles,
GaelCondeLosada and
alexandre-mrt
|
Additional code style and formatting rules are needed:
|
|
|
LGTM |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Global project structure has now been defined. Let's go through it:
screensfolder will contain all screens in the app. It is furthermore divided into flows:Onboarding,Registration,Profileetc. Each such folder can contain one or multiple screens, e.g.Registrationhas multiple screens:AuthenticationScreen,InterestsScreen,InformationScreen. Each screen has its' own folder with two files:___Screen.tsxandstyles.ts. One will contain the component itself and one will contain the style sheet for that screen. It is done for convenience, since style sheets can get extensively large. Feel free to add flows and screens based on our Figma mockup, but make sure to follow the conventions.componentsfolder consists of re-usable components that can be re-used in more than one screen, e.g.InputField(that will be re-used in the registration flow),LargeButton(a large wide button to proceed),SmallButton(you can already see many such small buttons in the Figma mockup). Each such component has its' own folder with two files - the same idea as with screens.navigationfolder will contain all navigation related items: navigation containers, stacks and tab navigators. This is where @alexandre-mrt will Set up React Navigation #9assetsfolder containsimagesandcolors. We defined a global file there to store the color definitions to not have to re-define colors each time, e.g.peachcolor that represents uniconnect branding stands for#FD9890.All in all, this will help us to structure the project files in a unified manner and will ultimately help us easily navigate over many files that will be created in the future. Please add your remarks and suggestions for further project structure improvement.