feat(indexer): route ProfileCount to Hyperindex - #236
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
8587b57 to
ab9e38b
Compare
Summary
Stacked on top of #235.
This PR migrates exactly one operation to Hyperindex:
ProfileCountEverything else remains Magic-backed.
Implementation details:
Adds a Hyperindex-specific query for
ProfileCount.Routes
ProfileCountthrough the per-operation backend switchboard tohyperindex.Keeps the public
/api/indexeroperation contract unchanged.Translates Magic's
excludeAuthorLabels: ["likely-test"]into Hyperindex's typed label predicate:Known parity note
At implementation time, the stage-specific sample returned:
ProfileCount:3388ProfileCount:3236This is a visible count difference on the welcome/landing stats. It appears to be due to backend indexing/label semantics rather than a client mapper change. Please manually verify whether this semantic difference is acceptable before merging.
What did not change
OrganizationCount,ActivityCount,ProjectCount,AwardCount,UserActivityCount, andActorWorkspaceCountsremain Magic-backed.Checks run
npm test -- src/app/api/indexer/__tests__/route.test.tsnpm run typechecknpx eslint src/app/api/indexer/route.ts src/app/api/indexer/__tests__/route.test.tsManual test instructions
Deploy this stacked branch after chore(indexer): add Hyperindex migration foundation #235.
Open
/welcomeor the landing surface that renders network stats.Confirm the users/profile count still renders without an error.
Confirm
/api/indexerresponses forProfileCountinclude:Confirm other count operations still report:
Rollback
Revert this PR or remove
ProfileCount: "hyperindex"fromOPERATION_BACKENDS. Other operations are unaffected.