Fix bullet warnings in dashboard page #2413
Merged
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.
Resolves #2373
Description
In the dashboard page, bullet was reporting some optimization to be done in the database queries that were used. I removed all of the warnings, by removing the unnecessary queries and adding the missing ones.
Type of change
How Has This Been Tested?
For the
bullet
warnings themselves, I manually tested if the warnings still showed up in the dashboard.bullet
also supports a configuration that makes a spec fail if abullet
warning is raised:This could be useful in the future, but it can be kind of confusing for beginners and it would require fixing all of the bullet warnings first.
I also had to change a scope in the
Donation
model to add anincludes
call. To make sure this change was safe, I improved the tests for this scope.Screenshots
No bullet warnings are shown anymore, yay \o/