Nutrition Tracker Feature #36
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 21 commits
November 11, 2020 10:25
…webapp-group6-importteamname-1 into m.abdelhamid Pulling from master
…webapp-group6-importteamname-1 into m.abdelhamid Resolving merge conflicts with master
… dedicated folder
… in get_consumed_recipe for loop
…webapp-group6-importteamname-1 into m.abdelhamid Merging from master
…webapp-group6-importteamname-1 into m.abdelhamid Merging from master
…webapp-group6-importteamname-1 into m.abdelhamid Merging from master
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After more than 30 hours of work on this feature, I am still not able to get it to work within the team's internal deadline. The backend and frontend functionality of this feature has been implemented, but there are still some errors that require resolving:
The Material UI toggle switch does not maintain its state when the page is refreshed. This causes a DB Integrity Error because after the user clicks the switch for the first time, the recipe is added to the consumed recipes DB table. However, when the page is refreshed, the switch reverts back to its initial state (un checked). When the user then presses the switch again, the application tries to add the recipe to the table, but it was previously added, which causes an Integrity Error.
When the "delete consumed recipe" endpoint is called, an error occurs, and the recipe is not removed from the table. The cause of this error is still unknown at this time.
The consumed recipes that are already stored in the consumed recipes DB table are not displayed in the Nutrition Tracker page. The Javascript frontend sees the returned response as empty, and displays the message "No recipes were consumed". The cause of this error is still unknown at this time.