Skip to content

🎨 Palette: Add helpful empty state to results dialog - #481

Draft
xbmc4lyfe wants to merge 1 commit into
mainfrom
palette-ux-improvement-empty-state-5595023871351808517
Draft

🎨 Palette: Add helpful empty state to results dialog#481
xbmc4lyfe wants to merge 1 commit into
mainfrom
palette-ux-improvement-empty-state-5595023871351808517

Conversation

@xbmc4lyfe

Copy link
Copy Markdown
Collaborator

πŸ’‘ What: Added an empty state <label> inside results-dialog.xml that appears when no results are found, displaying a message dynamically set via the empty_message window property. Updated _populate in results_dialog.py to set the correct message using localized strings.

🎯 Why: Previously, filtering out all results left the user with a confusing blank screen. This makes it clear that there are no results found.

πŸ“Έ Before/After: Before, it was a blank screen if there were 0 results. After, it shows a centered "No results found for {title}" or "No results after filtering for {title}" message.

β™Ώ Accessibility: Adds explicit messaging for an empty state rather than relying on visual absence of list items.


PR created automatically by Jules for task 5595023871351808517 started by @xbmc4lyfe

πŸ’‘ What: Added an empty state `<label>` inside `results-dialog.xml` that appears when no results are found, displaying a message dynamically set via the `empty_message` window property. Updated `_populate` in `results_dialog.py` to set the correct message using localized strings.

🎯 Why: Previously, filtering out all results left the user with a confusing blank screen. This makes it clear that there are no results found.

πŸ“Έ Before/After: Before, it was a blank screen if there were 0 results. After, it shows a centered "No results found for {title}" or "No results after filtering for {title}" message.

β™Ώ Accessibility: Adds explicit messaging for an empty state rather than relying on visual absence of list items.

Co-authored-by: xbmc4lyfe <273732874+xbmc4lyfe@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

πŸ‘‹ Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a πŸ‘€ emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions github-actions Bot added the addon label Aug 1, 2026
@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

βœ… No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 11 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: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: f7981f89-c2e9-40a8-ad3f-1532ff7bc29e

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between c8dfe60 and e5b4d80.

πŸ“’ Files selected for processing (2)
  • repo/plugin.video.nzbdav/resources/lib/results_dialog.py
  • repo/plugin.video.nzbdav/resources/skins/Default/1080i/results-dialog.xml

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.


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
Contributor

Up to standards βœ…

🟒 Issues 0 issues

Results:
0 new issues

View in Codacy

🟒 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

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.

@github-code-quality

Copy link
Copy Markdown

Code Coverage Overview

Languages: Python

Python / code-coverage/pytest

The overall coverage in commit e5b4d80 in the palette-ux-improveme... branch remains at 88%, unchanged from commit c8dfe60 in the main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant