I think my question has just been solved by another article, Clarified CQRS by Udi Dahan. The section “Commands and Validation” starts as follows: Commands and Validation In thinking through what could make a command fail, one topic that comes up is validation. Validation is different from business rules in that it states a context-independent … Read more
In the main file, use <script> to load the Javascript file x-counter.js. In the Javascript file, use fetch() to load the HTML code x-counter.html. In the HTML file, use <link rel=”stylesheet”> to load the CSS file x-counter.css. CSS file : x-counter.css button, p { display: inline-block; color: dodgerblue; } HTML file : x-counter.html <link rel=”stylesheet” … Read more
Yes it is possible, That is called as Separation of concern. You can create your component structure as below. MyComponentDirectory – useCustomHook – Component – helper The code will look like this one. Hook const useCustomHook = () => { const [value, setValue] = useState(”); const handleClick = (value) => { setValue(value) //do something. }; … Read more
At its heart, two models is about Separation of Concerns. I want my View to work off of a single Model. I want my Domain Model to represent the conceptual model I build with the domain experts. ViewModel often has technical constraints. Domain Model is about POCO, and not being bound by technical constraints of … Read more
I use an IBuilder interface and implement it using the ValueInjecter public interface IBuilder<TEntity, TViewModel> { TEntity BuildEntity(TViewModel viewModel); TViewModel BuildViewModel(TEntity entity); TViewModel RebuildViewModel(TViewModel viewModel); } … (implementation) RebuildViewModel just calls BuildViewModel(BuilEntity(viewModel)) [HttpPost] public ActionResult Update(ViewModel model) { if(!ModelState.IsValid) { return View(builder.RebuildViewModel(model); } service.SaveOrUpdate(builder.BuildEntity(model)); return RedirectToAction(“Index”); } btw I don’t write ViewModel I write Input … Read more
Single Responsibility Principle (SRP)- give each class just one reason to change; and “Reason to change” == “responsibility”. In example: Invoice class does not have a responsibility to print itself. Separation of Concerns (since 1974). Concern == feature of system. Taking care of each of the concerns: for each one concern, other concerns are irrelevant. … Read more