Fix custom page prefix scope (#2722)

Fixes #2721 

This PR removes frontend logic that set the seed-level scopeType for
custom page prefix workflows to `prefix`, which was causing the scope to
balloon larger than what users intended for some workflows.
This commit is contained in:
Tessa Walsh 2025-07-09 20:42:09 -04:00 committed by GitHub
parent 841c45fe59
commit a4b30c056d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -2640,12 +2640,7 @@ https://archiveweb.page/images/${"logo.svg"}`}
: [];
const primarySeed: Seed = {
url: primarySeedUrl,
// the 'custom' scope here indicates we have extra URLs, actually set to 'prefix'
// scope on backend to ensure seed URL is also added as part of standard prefix scope
scopeType:
this.formState.scopeType === ScopeType.Custom
? ScopeType.Prefix
: (this.formState.scopeType as ScopeType),
scopeType: this.formState.scopeType as ScopeType,
include:
this.formState.scopeType === ScopeType.Custom
? [...includeUrlList.map((url) => regexEscape(url))]