Skip to content

Fix Invoke-FuzzyScoop for nested Scoop bucket manifests - #383

Merged
kelleyma49 merged 1 commit into
kelleyma49:masterfrom
chengr025:fix/invoke-fuzzyscoop-nested-scoop-bucket-manifests
Jun 20, 2026
Merged

kelleyma49 merged 1 commit into
kelleyma49:masterfrom
chengr025:fix/invoke-fuzzyscoop-nested-scoop-bucket-manifests

Conversation

@chengr025

Copy link
Copy Markdown
Contributor

Invoke-FuzzyScoop currently enumerates only the direct children of each bucket's bucket directory. 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, fs shows entries like:

abyss/a
abyss/z

and the preview runs scoop info abyss/a, which fails.

This change recursively enumerates only *.json files and uses the manifest BaseName as the app name. Flat buckets continue to work as before, while nested buckets are now supported.

@kelleyma49
kelleyma49 merged commit e2abd8b into kelleyma49:master Jun 20, 2026
3 checks passed
@kelleyma49

Copy link
Copy Markdown
Owner

Merged. Thank you for your contribution!

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