It has been running for several months in ASP.NET MVC. I start to circle - I constantly come across Edit views, which are the same as Create views. Should I continue to just drop the editing views and try to make one view for the creation and editing? Since they are essentially the same, they perform the same check, the only difference is in the controller, where I update instead of Create. And I can do this with a simple if..else statement - if the object is found in the data store, update and then create.
What do you think? Is it possible that I will encounter problems in the future if I decide to get rid of "Editing"?
Clarification:
The main question: what changes / business requirements may arise, which will require separate creation / editing? This is actually what I would like to know. Because if we have a Page object that has, for example, these properties: Title, URL, Active, etc. And it requires that these fields be entered in Create, why do we allow them to be empty for any reason in Edit?
thank
source
share