Skip to content

fix: show actual filter values per project in OSS search results#368

Open
VivekArgSharma wants to merge 1 commit into
apsinghdev:mainfrom
VivekArgSharma:fix/filter-state-display
Open

fix: show actual filter values per project in OSS search results#368
VivekArgSharma wants to merge 1 commit into
apsinghdev:mainfrom
VivekArgSharma:fix/filter-state-display

Conversation

@VivekArgSharma
Copy link
Copy Markdown

Summary

  • Fixed unselected filter columns (popularity, stage, activity, competition) showing as blank (`-`) in OSS project search results
  • Now each project displays its actual computed values for all columns based on GitHub data

Changes

  1. packages/shared/types/projects.ts - Added stargazerCount, forkCount, pushedAt, createdAt to RepositoryProps
  2. apps/api/src/services/project.service.ts - GraphQL query fetches these new fields
  3. apps/web/src/utils/converter.ts - convertApiOutputToUserOutput computes actual filter values per-project from GitHub data instead of using user-selected filter values
  4. apps/web/src/components/ui/FiltersContainer.tsx - Updated call site

Before

When user selected e.g. Tech stack: Python + Competition: Very low, only the competition column was populated. All other columns showed `-`.

After

Every project row shows its actual popularity, stage, competition, and activity values regardless of which filters were applied.

fixes #364

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 23, 2026

@VivekArgSharma is attempting to deploy a commit to the AJEET PRATAP SINGH's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 23, 2026

Warning

Rate limit exceeded

@VivekArgSharma has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 57 minutes and 53 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 57 minutes and 53 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 42daa6be-2926-4e11-ba7d-cff909119f14

📥 Commits

Reviewing files that changed from the base of the PR and between a2ef5f3 and 3a9623c.

📒 Files selected for processing (4)
  • apps/api/src/services/project.service.ts
  • apps/web/src/components/ui/FiltersContainer.tsx
  • apps/web/src/utils/converter.ts
  • packages/shared/types/projects.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[GENERAL] Reset of Non-Active Filter States on Single Selection In OSS Projects Search Results

1 participant