Conversation
There was a problem hiding this comment.
@dofelor Thanks for the submission. For every project starting with the Habit Tracker one of the requirements is a Readme with:
✅ Reflection on your experience while developing it (ideally written with your own words). This is the most important part of the Readme.
✅ Instructions on how to run the project
✅ Explain what the app does and how it works
✅ Explain architectural choices
Please add that before we can review. After making your changes, just commit and push, no need for a new pull request 😊.
💁♂️If you have any questions, the best way to get help is in our Discord, in the #get-help-with-projects channel.
Added project overview, SQL course experience, and tech stack details.
Added features and usage instructions for the habit tracker application.
TheCSharpAcademy
left a comment
There was a problem hiding this comment.
@dofelor Thanks for submitting and apologies for the delay! There's a big problem in your project that you need to solve before moving forward:
You can't let users create tables in your database. Every habit entered by the user becomes a new SQLite table:
That's unnecessarily complex and defeats the point of relational data. A habit should normally be data, not database schema. To solve this use a table for habits and a table for records, linked by a Foreign Key.
💁♂️If you have any questions, the best way to get help is in our Discord, in the #get-help-with-projects channel.
No description provided.