Repository navigation
Fix Invoke-FuzzyScoop for nested Scoop bucket manifests - #383
Merged
kelleyma49 merged 1 commit intoJun 20, 2026
Merged
kelleyma49 merged 1 commit into
kelleyma49 merged 1 commit into
Conversation
Owner
|
Merged. Thank you for your contribution! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Invoke-FuzzyScoop currently enumerates only the direct children of each bucket's
bucketdirectory. This works for traditional flat buckets, but it treats subdirectories as apps when a bucket organizes manifests in nested folders.Scoop supports manifests in subfolders, and some buckets use this layout. For example, abgox/abyss stores manifests under paths such as:
bucket/a/abgox/abgox.scoop-i18n.json
Before this change,
fsshows entries like:abyss/a
abyss/z
and the preview runs
scoop info abyss/a, which fails.This change recursively enumerates only
*.jsonfiles and uses the manifest BaseName as the app name. Flat buckets continue to work as before, while nested buckets are now supported.