feat(of-the-day): user-customizable fonts/colors/offsets via x-style-elements (v1.3.0) - #188
Conversation
…elements (v1.3.0) First adopter of the core's x-style-elements system: the schema declares two styleable elements (title_text, body_text) in ~20 lines and the core expands them into full font/size/color/x-y-offset config blocks — no hand-copied property blocks, and the plugin code resolves them through src.element_style in one helper. Purely additive: with an untouched config (bare, or carrying the schema defaults the web UI bakes in on every save) rendering is byte-identical to v1.2.0 (verified across 5 sizes x both screens x both config shapes). On older cores the declaration is simply not expanded (no customization UI appears) and a guarded import keeps the classic styling path. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FqzC1nzTWL4kaqgMaQZFam
|
Warning Review limit reached
Next review available in: 58 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ 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 |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 12 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
…ssignment - Remove unused `from datetime import date` (F401). - Remove dead `style = ...` assignment that was never read (F841) — the resolver is accessed directly via p._element_style_resolver two lines later. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KEZK1P1Q1fu5pcuVrkrCFZ
1 participant
Summary
First adopter of the core x-style-elements system (ChuckBuilds/LEDMatrix#394): the schema declares two styleable elements (`title_text`, `body_text`) in ~20 lines and the core expands them into full font/size/color/x-y-offset config UI — the plugin had zero customization before and gains all of it with one small helper in the renderer.
Purely additive: with an untouched config (bare, or carrying the schema defaults the web UI bakes in on every save) rendering is byte-identical to v1.2.0. On older cores the declaration is simply not expanded (no new UI appears) and a guarded import keeps the classic styling path.
Verification
🤖 Generated with Claude Code
https://claude.ai/code/session_01FqzC1nzTWL4kaqgMaQZFam