feat: Optimize potato calculations and notifications #366
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.
Fixes GIBPOTATO-BACKEND-NK. The issue was that: Uncached
potatoSentTodayandpotatoLeftTodaymethods execute identical SUM queries multiple times during validation and notification.potatoSentToday()to avoid duplicate queries.potatoSentToday()inpotatoLeftToday().potatoLeftTodayvalue to the notification service to avoid re-querying.This fix was generated by Seer in Sentry, triggered by Michi Hoffmann. 👁️ Run ID: 2903740
Not quite right? Click here to continue debugging with Seer.