-
Notifications
You must be signed in to change notification settings - Fork 5
π¨ Palette: Add empty state message to results dialog #485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
xbmc4lyfe
wants to merge
1
commit into
main
Choose a base branch
from
palette-add-empty-state-message-to-results-dialog-2551422589044269587
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π Maintainability & Code Quality | π‘ Minor | β‘ Quick win
π§© Analysis chain
π Script executed:
Repository: Appz4Fun/nzbdavkodi
Length of output: 591
π Script executed:
Repository: Appz4Fun/nzbdavkodi
Length of output: 1335
π Web query:
Kodi skin strings.po messageid comment string IDs start numbering resource.language strings.po 30001π‘ Result:
In Kodi development, string IDs in strings.po files are used to localize user interface text, and specific numeric ranges are reserved for different types of add-ons [1][2]. These IDs are encoded in the msgctxt field of the GNU Gettext-formatted strings.po file using the syntax msgctxt "
#ID" [1][3]. The reserved numeric ranges for string IDs are as follows: * 30000 thru 30999: Reserved for plugins and plugin settings [1][2] * 31000 thru 31999: Reserved for skins [1][2] * 32000 thru 32999: Reserved for scripts [1][2] * 33000 thru 33999: Reserved for common strings used in add-ons [1][2] For a skin, you should use an ID within the 31000β31999 range [1][4]. While some users have historically experimented with IDs outside these ranges, the system is designed to enforce these boundaries, and using an ID outside the designated range for your add-on type may result in the label failing to display correctly in the GUI [5]. If you are working within a skin, ensure your entry follows the required format: msgctxt "#31001" msgid "Your string text" msgstr "" If you need to access a string from an add-on within a skin, it is recommended to use the $ADDON[addon.id stringID] format rather than the standard $LOCALIZE[ID] function, as this explicitly targets the correct add-on's string resource [5]. For plugin-specific settings, IDs like 30001 are standard practice within the allocated 30000β30999 range [1][6].Citations:
Use a skin-localized empty-state string.
No results foundis hardcoded in a skin XML, while Kodi skin strings use the#31000β#31999range with$LOCALIZE[...]. ExistingNo results found for {}entries use plugin string IDs, so this empty list text should not reuse those IDs.π€ Prompt for AI Agents