-
Notifications
You must be signed in to change notification settings - Fork 132
Fix case mismatch in citation key lookup #1141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Bib keys were lowercased during parsing but Doxygen HTML preserves original case, causing all author-prefix lookups to fail silently. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
CodeAnt AI is reviewing your PR. Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
📝 WalkthroughWalkthroughA function in the documentation processing module was updated to preserve the original case of bibliography entry keys in its returned dictionary, rather than converting them to lowercase. The docstring was updated accordingly to reflect this behavioral change. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR fixes a bug in the documentation citation post-processing script where bib keys were being lowercased during parsing but Doxygen HTML preserves the original case in citation anchors, causing all author-name lookups to fail silently.
Changes:
- Removed
.lower()call inparse_bib_authors()so dictionary keys match the case-sensitive format used by Doxygen anchors (e.g.,Allaire02instead ofallaire02)
Nitpicks 🔍
|
|
CodeAnt AI finished reviewing your PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1141 +/- ##
=======================================
Coverage 44.03% 44.03%
=======================================
Files 70 70
Lines 20649 20649
Branches 2054 2054
=======================================
Hits 9093 9093
Misses 10368 10368
Partials 1188 1188 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
User description
Summary
parse_bib_authors()stored bib keys lowercased (e.g.allaire02), but Doxygen HTML preserves the original case inCITEREF_anchors (e.g.Allaire02), so all author-prefix lookups inprocess_html()andcheck_bare_citations()failed silently.lower()call so keys match naturally between the bib parser and Doxygen outputTest plan
cmake -D MFC_DOCUMENTATION=ONand verify author prefixes appear before citation numberspython3 docs/postprocess_citations.py --check <html_dir>and confirm no bare citations are reported🤖 Generated with Claude Code
CodeAnt-AI Description
Preserve original BibTeX key case so citation author prefixes match generated docs
What Changed
Impact
✅ Citations show author prefixes in generated docs✅ Fewer false positive citation errors during docs checks✅ Consistent citation linking between .bib and Doxygen HTML💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit