feat: add ProjectBadgeView and RepoBadgeView for tracking project and repo visit counts #3214
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.
Optimize and Refactor
ProjectBadgeView
for Enhanced Performance and AccuracyDescription:
This pull request introduces a significant update to the
ProjectBadgeView
class, focusing on performance optimization, improved logic for tracking unique visits, and better handling of edge cases.Key Changes:
Optimized Visit Tracking:
Improved Logic for Data Management:
IP
visit records if the last visit was on a previous day, ensuring accurate daily tracking.Enhanced Visualization:
Code Simplification and Maintenance:
F
expressions for atomic updates to the project visit count, preventing race conditions.Performance Improvements:
IP
objects.Why These Changes?
The old implementation had several inefficiencies:
The updated code resolves these issues and ensures accurate, efficient, and scalable tracking of project visits.
@DonnieBLT sir , can you please review this new PR ?
another step for fix #2972