ASP.NET MVC - Proper approach to CRUD-based resource management + Forms?
Hello,
I have a simple question that I need to cover before I progress further.
I'm builiding an app on ASP.NET MVC & Angular, I have views with forms ready to be sent - but I've got stuck at routing.
My issue is - my Resource model has CRUD generated for it and it's attached to /api route.
What should I do with my views containing forms to pass to these api routes?
Should I overload the CRUD functions with argumentless alternatives that return views or should I attach routes directly to views (if possible) - or would it be an anti-MVC pattern?
0 comments:
Post a Comment