Client-side routing
Our master-detail relationship is indeed working, yet it has some major flaws. The current in-page navigation approach, for example, is completely different from the original plan. We wanted our users to switch back and forth between the Welcome View and a dedicated Item Detail View, but instead we're opening a detail panel under the first one. No, not just one. Three different panels, one for each item list. That doesn't make any sense! We need to fix that as soon as possible.
While doing that, we also have another severe issue to solve. You might have noticed that regardless of what we do within our app, the URL in the browser's address bar is always the same. This means that we won't be able to share, say, a URL that will ...
Get ASP.NET Core: Cloud-ready, Enterprise Web Application Development 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.
