fix(slides): make IconPark JSON output encoding-safe - #2484
Conversation
|
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)
Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe IconPark CLI now emits JSON with escaped non-ASCII characters. Tests can set subprocess environment variables and verify valid, ASCII-safe output under ChangesIconPark JSON output
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The change makes IconPark JSON safe for non-UTF-8 Windows locales while preserving decoded values; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Summary
Keep IconPark's machine-readable stdout usable on non-UTF-8 Windows locales by emitting non-ASCII JSON characters as standard escape sequences. JSON consumers receive the same decoded values without depending on the console code page.
Changes
PYTHONIOENCODING=cp1252.Test Plan
python skills/lark-slides/scripts/iconpark_tool_test.py -k non_utf8_stdoutPYTHONUTF8=1 python skills/lark-slides/scripts/iconpark_tool_test.py(21 tests)python -m py_compile skills/lark-slides/scripts/iconpark_tool.py skills/lark-slides/scripts/iconpark_tool_test.pynode scripts/skill-format-check/index.jsPYTHONIOENCODING=cp1252returned parseable JSONRelated Issues
Summary by CodeRabbit
Bug Fixes
Tests