Remove unnecessary FoodItem instantiation before Firestore persistence #229
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.
The
addProductmethod created aFoodItemobject that was never persisted—only a separately constructedfoodItemDatamap was written to Firestore. This caused unnecessary object allocation and obscured which data structure was actually being stored.Changes
FoodIteminstantiation before Firestore writeFoodItemonly after successful persistence, using the generated document IDappendToCsvcall instead of referencing unused objectBefore:
After:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.