Pyq aiml#69
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 56 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (16)
📝 WalkthroughWalkthroughThis PR updates previous-year-question (PYQ) JSON datasets across multiple RGPV subject files in AIML (semesters 3-4) and Common (semesters 1-2) directories. Changes replace exam metadata, question/subQuestion text, unit/type classifications, and isPredicted flags across numerous exam papers, and populate an empty papers array for al-401. ChangesPYQ Content Data Updates
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
Suggested reviewers: ✨ 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 |
🎉 Congratulations @nitinmohan18!Thank you for contributing to HyperLearningTech. Your pull request has been successfully merged into main. 📦 Merge Summary
🚀 Keep Contributing
Thank you for helping make HyperLearningTech better. Happy Coding! 🚀 |
Pull Request
Summary
This PR adds the latest Previous Year Questions (PYQs) for AL-401 and fixes a global sorting issue across all subjects to ensure that the newest papers (by year/month) always appear at the top.
Related Issue
Closes #
Type of Change
What Changed?
pyqs.jsonfiles in thecontent/directory.papersarray across all subjects globally so students always see the latest exams first.Screenshots (UI Changes Only)
N/A - Data changes only.
Testing
content/rgpv/aiml/semester-4/al-401/pyqs.jsonhas the correct schema and contains all the new papers.al-301,bt-101, etc.) were properly formatted and sorted with 2025 and 2024 papers explicitly at the top of thepapersarray.Checklist
Before requesting a review, confirm the following:
main.npx prettier --write <file>).npm run format:checkpasses.npm run lintpasses.npm run typecheckpasses.npm run buildpasses.Additional Notes
You may want to run
npm run format:check,lint, andtypecheckbefore merging, but since these were just.jsondata file updates, there shouldn't be any build issues!Summary by CodeRabbit
New Features
Bug Fixes