code design - Page 164 - Developer IT

When following SRP, how should I deal with validating and saving entities?

- by Kristof Claes

I've been reading Clean Code and various online articles about SOLID lately, and the more I read about it, the more I feel like I don't know anything. Let's say I'm building a web application using ASP.NET MVC 3. Let's say I have a UsersController with a Create action like this: public class UsersController : Controller { public ActionResult Create(CreateUserViewModel viewModel) { } } In that action method I want to save a user to the database if the data that was entered is valid. Now, according to the Single Responsibility Principle an object should have a single responsibility, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility. Since validation and saving to the database are two separate responsibilities, I guess I should create to separate class to handle them like this: public class UsersController : Controller { private ICreateUserValidator validator; private IUserService service; public UsersController(ICreateUserValidator validator, IUserService service) { this.validator = validator; this.service= service; } public ActionResult Create(CreateUserViewModel viewModel) { ValidationResult result = validator.IsValid(viewModel); if (result.IsValid) { service.CreateUser(viewModel); return RedirectToAction("Index"); } else { foreach (var errorMessage in result.ErrorMessages) { ModelState.AddModelError(String.Empty, errorMessage); } return View(viewModel); } } } That makes some sense to me, but I'm not at all sure that this is the right way to handle things like this. It is for example entirely possible to pass an invalid instance of CreateUserViewModel to the IUserService class. I know I could use the built in DataAnnotations, but what when they aren't enough? Image that my ICreateUserValidator checks the database to see if there already is another user with the same name... Another option is to let the IUserService take care of the validation like this: public class UserService : IUserService { private ICreateUserValidator validator; public UserService(ICreateUserValidator validator) { this.validator = validator; } public ValidationResult CreateUser(CreateUserViewModel viewModel) { var result = validator.IsValid(viewModel); if (result.IsValid) { // Save the user } return result; } } But I feel I'm violating the Single Responsibility Principle here. How should I deal with something like this?

Search Results

Search found 97231 results on 3890 pages for 'code design'.

Page 164/3890 | < Previous Page | 160 161 162 163 164 165 166 167 168 169 170 171 | Next Page >

- by Kristof Claes

- by Geo

- by Geek

- by John Blumenauer

- by Essam

- by TomatoSandwich

- by John.Weland

- by AK

- by Rig Veda

- by Chris Walton

- by Malfist

- by Mark Knol

- by schnieds

- by johncarl

- by B?????

- by David Moreno García

- by SonOfPirate

- by Hugo Kornelis

- by Roland Schneider

- by Srikar

- by Vaishak Suresh

< Previous Page | 160 161 162 163 164 165 166 167 168 169 170 171 | Next Page >