Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Charlottelaw/jdi-7-navigation-drawer #23

Merged
merged 42 commits into from
Nov 20, 2024

Conversation

CharlotteLaw
Copy link
Contributor

@CharlotteLaw CharlotteLaw commented Oct 26, 2024

What's new in this PR

Description

[Updated my old PR as of Nov 17] Used the Drawer Navigation documentation in React Native to create a side-bar for navigation for the Hope for Healing Guide. Created subsection functionality so that when you click Chapter 1, there is a drop down for subsections.

Screenshots

IMG_1389

How to review

All of my changes were only in the src/screens/HealingResources/HopeHealingGuide/index.tsx file. You can take a look at that whole file. The ChapterOneNavigator() may error out in prettier/eslint because it is unused but I am keeping it here because I will be using it in the future for stack navigation within chapters. The Drawer.Navigator wrapper in the export function for HopeHealingGuide stores the screen logic for now.

Next steps

Look at Angeline's PR to see how she did the accordion menu so I can use similar implementation for the Chapter drop down to display the subsections of each chapter. Later on, I will use a map function to dynamically display out all the drawer navigation screens instead of brute-forcing it like what we are doing right now.

Relevant links

Online sources

https://reactnavigation.org/docs/drawer-based-navigation

Related PRs

Not sure yet?

CC: @philipye314

Copy link
Collaborator

@philipye314 philipye314 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just leaving this here for reference: Work on making the Drawer.Screen components into dropdowns, and make the subheading components just clickable buttons. We'll worry about subheading routing later.

@arfamomin arfamomin mentioned this pull request Nov 17, 2024
@CharlotteLaw CharlotteLaw dismissed philipye314’s stale review November 18, 2024 08:41

The merge-base changed after approval.

philipye314
philipye314 previously approved these changes Nov 18, 2024
Copy link
Collaborator

@philipye314 philipye314 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@philipye314 philipye314 merged commit 13c7816 into main Nov 20, 2024
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants