Our main focus now is to implement a standard master/detail navigation pattern. We’ll do that in two consecutive steps to demonstrate all the relevant Angular features better, as follows:
- Put together a temporary, component-based master/detail relationship within the same view using the Angular data-binding capabilities.
- Improve that temporary code, replacing the single-view display with an actual view-based navigation pattern with full client-side routing support.
Truth be told, the former step isn’t needed at all; we could just implement the latter and get the task over with. However, by choosing that quick and straight path, we would skip some really important concepts regarding Angular and its interactions with the web API structure we just built. We’re talking about something that will come in handy later on, so it’s highly recommended that we restrain ourselves from rushing things.