fix(scan): correct param handling to respect user provided values (#566)

the `applyDefaultSettings` was doing null check a little wrong and as a result the default param were always applied.
NeuraLegion · Jul 19, 2024 · a62549d · a62549d
1 parent b2f604b
commit a62549d
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/src/Scan/RestScans.ts b/src/Scan/RestScans.ts
@@ -150,9 +150,9 @@ export class RestScans implements Scans {
     scanConfig: Omit<ScanConfig, 'headers'>
   ): Promise<Omit<ScanConfig, 'headers'>> {
     const attackParamLocations =
-      scanConfig.attackParamLocations ?? scanConfig.templateId
-        ? undefined
-        : [...ATTACK_PARAM_LOCATIONS_DEFAULT];
+      scanConfig.attackParamLocations ??
+      (scanConfig.templateId ? undefined : [...ATTACK_PARAM_LOCATIONS_DEFAULT]);
+
     const exclusions =
       scanConfig.exclusions?.params || scanConfig.exclusions?.requests
         ? scanConfig.exclusions