fix: correct feedback sentiment and tech partner metrics - #91
Open
nehayadav827 wants to merge 1 commit into
Open
nehayadav827 wants to merge 1 commit into
nehayadav827 wants to merge 1 commit into
Conversation
|
@nehayadav827 is attempting to deploy a commit to the SEETA's projects Team on Vercel. A member of the Team first needs to authorize it. |
Open
58 tasks
This file contains hidden or 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
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.
Description
This PR fixes two data correctness issues in
src/lib/data-processing.tsrelated to BuilderOS analytics and contribution metrics.What problem does it solve?
feedbackSentimentpreviously hardcoded neutral and negative feedback counts to0, preventing the dashboard from surfacing actual sentiment distribution.calculateTechPartnerMetrics()grouped directly byWhich Tech Partner, causing values like"Libp2p, Storacha"to be treated as a single combined partner instead of separate normalized partners.Relates to #68
Changes
calculateNeutralFeedback()andcalculateNegativeFeedback()feedbackSentimentto use real calculated valuescalculateTechPartnerMetrics()to usenormalizeTechPartners()-[x] Kept changes scoped to
src/lib/data-processing.tsScreenshots / Demo
Updated feedback sentiment flow
Updated tech partner normalization logic
Diff statistics and formatting validation
Additional Notes
Validation performed:
git --no-pager diff --checkpasses successfully.npm run lintcurrently opens the interactive Next.js ESLint setup prompt.src/lib/__tests__/utils.test.ts.No breaking changes introduced.
Checklist