chore: footer social handles + splice-sdk-nav lint nits - #114
Conversation
- docs.json footer: x and linkedin handles -> resqsystems_inc / resq-systems-inc (the twitter:site/creator metatags still read @ResQSoftware; left for a follow-up decision). - splice-sdk-nav.py: ruff nits only — unused loop vars renamed to _, ambiguous 'l' -> 'k', explicit encoding='utf-8' on read/write_text. No behavior change. From uncommitted work on fix/api-docs-partial-failure-guard.
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughUpdated footer social URLs and refined the SDK navigation splicing script to emit page IDs and use explicit UTF-8 encoding when processing ChangesSocial link updates
SDK navigation generation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Small riders from the
fix/api-docs-partial-failure-guardbranch, landed onto current main.x→resqsystems_inc,linkedin→resq-systems-inc._, ambiguousl→k, explicitencoding=\"utf-8\"onread_text/write_text. No behavior change;ruff checkclean, compiles.One thing to decide
The
twitter:site/twitter:creatormetatags indocs.jsonstill read@ResQSoftware— your footer change didn't touch them, so I left them. If the X handle is nowresqsystems_inc, those two metatags are stale too. Want me to update them in a follow-up, or are they intentionally different?Summary by CodeRabbit
New Features
Documentation