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:
parent
841c45fe59
commit
a4b30c056d
@ -2640,12 +2640,7 @@ https://archiveweb.page/images/${"logo.svg"}`}
|
|||||||
: [];
|
: [];
|
||||||
const primarySeed: Seed = {
|
const primarySeed: Seed = {
|
||||||
url: primarySeedUrl,
|
url: primarySeedUrl,
|
||||||
// the 'custom' scope here indicates we have extra URLs, actually set to 'prefix'
|
scopeType: this.formState.scopeType as ScopeType,
|
||||||
// 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),
|
|
||||||
include:
|
include:
|
||||||
this.formState.scopeType === ScopeType.Custom
|
this.formState.scopeType === ScopeType.Custom
|
||||||
? [...includeUrlList.map((url) => regexEscape(url))]
|
? [...includeUrlList.map((url) => regexEscape(url))]
|
||||||
|
Loading…
Reference in New Issue
Block a user