In most Blazor WASM CRUD examples editing is performed by navigating to a dedicated page. This is a breakdown of what is the common example I have found after many searches...
Initial page contains a grid component
Each detail row has an "Edit" button or link
Clicking the button navigates to a new page dedicated to editing
The edit page retrieves the id of the model of interest
In the initialization of the page or dedicated edit component within makes a call to a Web API requesting the model to be edited
The edit form contains "Cancel" and "Save"
Save will usually send a HTTPPUT to update the model and retrieve the response
Some sort of user notification (Toast Message) is provided
When successful the navigation manager is used to return to the initial page containing the grid which inherently pulls a fresh copy of data
In my application I am required to mimic a Windows Desktop application.
One page consists of a list and an edit area
The user selects an item on the list
The items editable details are displayed directly adjacent to the list
The user has a save button to commit the changes
If the user attempts to select a different item and changes have been made they are provided a confirmation informing them that changes have been made and do they want to discard and continue
Is there a Blazor pattern that allows for a list component and a form editing component to be used on a single page?
