This is where my stuff & what Apple continues started to differ slightly. My ‘hikeData.json’ names a park with many hiking trails where the World’s Fair in 1960 was held. I wonder why we don’t do a ‘World’s Fair’ anymore. 🤷‍♂️

This chapter moved pretty quickly, the biggest hangup I had was mis-naming one of the ‘Hike’ properties heartRate. Instead I put heartRage 😅 😤 I took a break then found the error the next morning.
Aside from the hangup, this chapter was pretty fun. HikeView has an animation that dismisses the view by shrinking it and reducing its opacity.
I had an idea to make it raise up- until I saw the view was animating over everything & it did not look good.
.asymmetric(insertion: .move(edge: .trailing), removal: .move(edge: .top)) // LOOKS AWFUL 🙅‍♂️
What about it looks so bad? Well, place my change in HikeView.swift after you complete what Apple gives you. You may notice the animation flies over the original button, looking broken. Seems like there should be a layer we can tell the system to dismiss the animation from underneath, that would be nice.