I have written a basic MVC application and am seeking feedback upon its implementation and coding style. Please help me improve it any any way. Thank you in advance.
Thank you so much
1 Like
Take this with a grain of salt. It doesn’t feel like a traditional Model View Controller design pattern in my opinion. Models typically can be typically represented as a table in a database with records. All you have is a single data field of a count. Also typically you have multiple “actions” for an implementation of the model view controller pattern. One for viewing data, one for updating data, one for deleting data, and one for adding data. Lastly there is typically multiple “views” involved in an MVC pattern. At minimum a way to view your data, add your data, edit your data, and delete your data.
While it is a very cool simple app prototype, I would not call it an Model View Controller app.
1 Like
Thank you so much for taking the time to look and provide some feedback =) I actually had some conversations with another individual earlier about similar controversies about what actually updates what.
In a full project I’ve contributed to following this same logic, we used fetch to import a collection of tasks and store them on the app.state. The user can view a list of all tasks, add new ones, remove a task edit a task, mark task as completed, cycle priority, mark entire group as done, etc.
I thought those were considered CRUD operations?
Hello
You are covering “read” and “update” with your app. For a full CRUD app, the user needs to be able to “create” and “delete” data, and generally be able to store the changes somewhere.
1 Like
No idea what MVC is about but looks cool.
1 Like