Why bother?

Wait a minute... why did we have to pass the whole quiz object, since we're only using it to get the quiz ID? Can't we just forget about it as a whole and just pass the quiz ID from the QuizEditController? We won't need to wait for any async call, as we're already getting it from the route! Why should we complicate the task with all this ngOnChanges() fuzz?

This is a legitimate question, especially now that the app is still in its embryonic stage, we can definitely afford to have a component that will serve all the available questions for a given quiz without knowing anything about the quiz itself, other than its ID. We can even say that, for the time being, working with the quiz ID and forgetting about the rest would be the right ...

Get ASP.NET Core 2 and Angular 5 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.