Checkpoint: Navigation and State

Question 1 of 5

• src/app/hikes/photos/[id].tsx
• src/app/(hikes)/[id]/photos.tsx
• src/app/hikes/[id]/photos.tsx
• src/components/HikePhotos.tsx

Question 2 of 5

• A red error screen, because Number(“abc”) throws.
• A friendly “hike not found” state, because the lookup returns nothing and the screen handles that case.
• The first hike in the list, as a fallback.
• Nothing; Expo Router refuses to match non-numeric ids.

Question 3 of 5

• A second copy of the log is pushed on top of the first, so the back gesture returns to the deleted hike’s screen.
• The tab bar disappears permanently.
• The hikes reducer runs twice.

Question 4 of 5

• Components that read hikes never re-render when hikes change.
• It makes the reducer run on a background thread.
• It removes the need to return new arrays from the reducer.
• A delete button that only uses dispatch doesn’t re-render when the list changes, because the dispatch context never changes.

Question 5 of 5

• autoFocus on the Save button.
• behavior="height" on the KeyboardAvoidingView.
• keyboardShouldPersistTaps="handled" on the ScrollView that contains the form.
• submitBehavior="blurAndSubmit" on the last input.