Skip to content

chore(lacrosse-scoreboard): move fine-tuning config fields behind Advanced Settings (x-advanced) - #207

Closed
ChuckBuilds wants to merge 1 commit into
mainfrom
claude/chuck-builds-plugin-config-65322r-lacrosse-scoreboard
Closed

chore(lacrosse-scoreboard): move fine-tuning config fields behind Advanced Settings (x-advanced)#207
ChuckBuilds wants to merge 1 commit into
mainfrom
claude/chuck-builds-plugin-config-65322r-lacrosse-scoreboard

Conversation

@ChuckBuilds

Copy link
Copy Markdown
Owner

Pull Request

Summary

Applies the "easy stuff up front, power stuff behind one click" treatment (LEDMatrix core PR #417's x-advanced mechanism) to lacrosse-scoreboard's config_schema.json: 93 of 127 flat fields are now flagged "x-advanced": true, so the core web UI collapses them into one "Advanced Settings" section at the bottom of the config page. Purely additive schema-data change — no field removed or renamed, no default or required changed, no manager.py change.

Type of change

  • Bug fix in an existing plugin
  • New plugin (also fill out the SUBMISSION.md checklist below)
  • New feature for an existing plugin
  • Documentation only
  • Repo-wide change (registry script, hook, top-level docs)
  • UX-only config schema reorganization (no behavior change)

Plugin(s) affected

lacrosse-scoreboard

Related issues

N/A — part of the plugin-store-wide config UX uplift following LEDMatrix core PR #417.

Test plan

  • Loaded the plugin in LEDMatrix on real hardware
  • Loaded the plugin in LEDMatrix emulator mode (EMULATOR=true python3 run.py)
  • Rendered the plugin in the dev preview server (scripts/dev_server.py)
  • Verified the web UI configuration form against the schema
  • N/A — repo-wide / docs-only change

Details: schema still parses as strict JSON; flags inserted via text patch preserving the file's 2-space indent and unicode escapes; verified programmatically that recursively stripping every x-advanced key yields a schema deep-equal to main, and that no object-type property carries the flag; update_registry.py --dry-run reported changes for this plugin only. Rendering was not eyeballed against a live core web UI in this environment — the flags use exactly the mechanism core already ships.

Required for plugin changes

  • Bumped version in plugins/<id>/manifest.json (1.4.0 → 1.4.1, with a versions[] changelog entry)
  • class_name in manifest.json matches the actual class in manager.py exactly (unchanged)
  • entry_point matches the real file (unchanged)
  • Updated the plugin's README.md if config keys changed (no keys changed — N/A)
  • config_schema.json is the source of truth for the web UI form — no new options added, only x-advanced render hints
  • Pre-commit hook ran successfully (update_registry.py run directly; plugins.json synced to 1.4.1)

Checklist

  • My commits follow the message convention in CONTRIBUTING.md
  • I read CONTRIBUTING.md and CODE_OF_CONDUCT.md
  • I've not committed any secrets

Notes for reviewer

What was flagged advanced, and why (one line each):

  • defaults.update_interval_seconds / defaults.season_cache_duration_seconds — poll-interval and cache-TTL tuning with sane defaults.
  • defaults.show_odds — betting odds, off by default and niche; defaults.show_shots — README says leave off (ESPN doesn't publish the stat yet).
  • Per-league (ncaa_mens / ncaa_womens, uniformly): scroll_settings.* (6 fields) — scroll fine-tuning; teams.exclude_teams — niche spoiler-protection list; teams.favorite_live_boost — rotation-weight knob; update_intervals.* (5 fields) — per-mode poll intervals; display_durations.* (5 fields) — per-league overrides of the basic defaults.display_duration; display_options.show_odds / show_shots — off-by-default niche toggles; mode_durations.* — null-default overrides; dynamic_duration.* — opt-in duration fine-tuning, off by default.
  • customization.* — per-element font overrides (6 text elements) and pixel-offset layout overrides (all default 0).

Kept basic (never flagged): enabled (required), league enable toggles + favorite_teams / favorite_teams_only / show_all_live, display_modes.* including the switch/scroll mode enums (headline feature in this plugin's README quick-start), filtering.recent/upcoming_games_to_show (also in the quick-start example), live_priority, defaults.display_duration, and the show_records / show_ranking toggles (rank badges are a headline feature).

Note: schema/manifest_schema.json doesn't exist in this repo checkout, so manifest validation is left to CI's manifest check.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LFNedFLmEcSHqSHG9Lwa62


Generated by Claude Code

…anced Settings (x-advanced)

UX-only schema reorganization for a quicker first-time setup. No fields
removed or renamed, no defaults changed, no validation change.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LFNedFLmEcSHqSHG9Lwa62
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@ChuckBuilds, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c568c3e7-1c44-4c98-afba-21e735dfad0d

📥 Commits

Reviewing files that changed from the base of the PR and between 3ba5905 and 5f8b175.

📒 Files selected for processing (3)
  • plugins.json
  • plugins/lacrosse-scoreboard/config_schema.json
  • plugins/lacrosse-scoreboard/manifest.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/chuck-builds-plugin-config-65322r-lacrosse-scoreboard

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

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.

Copy link
Copy Markdown
Owner Author

Closing in favor of the consolidated PR #208 (per maintainer request, all x-advanced schema uplifts in one PR — this plugin's change is included there as its own commit).


Generated by Claude Code

@ChuckBuilds
ChuckBuilds deleted the claude/chuck-builds-plugin-config-65322r-lacrosse-scoreboard branch August 5, 2026 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants