Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I think it is still doing on the minimum actions required..for this <strong>"Action"</strong> may not fit the Absolute single responsbility - but it is <strong>single action</strong></p> <ol> <li><p>The the attributes are saying to ASP.NET that this <strong>method</strong> will only work with HTTP.Post, and identity that is trying to use it must be authorised. - Good Security. So at this point nothing is actually being done. These are just telling the server what to check. </p> <p>ie if not HTTP.post <strong>method will not work</strong>, and if your not the list, <strong>wont work</strong>.</p></li> <li><p>There is validation to check if the user Identity matchs those of the dinner. - Sanity Check.</p></li> <li><p>This is based on Strong Type Checking - do UpdateModel(dinner) - is just making sure that the current objects in the model have been updated with the new data, then the repository is called to Save(). - This is still in the one unit of action - updating the model so that we can call save and persist.</p></li> <li><p>Validation checks are handled in the Catch which is adding RuleViolations to the Model, and returning the user back to the offending view - ie edit/create partial view which is passing responisbility to that to deal with.</p></li> <li><p>If the save works - its is just moving the "workflow" of the user to the Details - i.e clearing the form from memory and moving the work back to the details. IMHO great as - we are in a POST scenario and stuff not lying around in memory - Good.</p></li> <li><p>It would be easier not to move the flow to back the details and just leave on the partial edit view.</p></li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload