Skip to content

Preserve Bulk Replay attack configuration - #91

Open
harryadel wants to merge 1 commit into
repplus:mainfrom
harryadel:fix/bulk-replay-config-persistence
Open

harryadel wants to merge 1 commit into
repplus:mainfrom
harryadel:fix/bulk-replay-config-persistence

Conversation

@harryadel

Copy link
Copy Markdown

Summary

  • keep the Bulk Replay action available after opening an unmarked attack result
  • retain the original marked request as the source for rerunning an attack
  • remember attack type, per-position payloads, number ranges, and Battering Ram selections when reopening the modal
  • keep Battering Ram settings separate so switching modes does not overwrite position-specific choices
  • add focused UI regression coverage for reopening completed and dismissed attacks

Testing

  • npx vitest run tests/bulk-replay-config-ui.test.js (2 passed)
  • npm run package
  • Full suite: 168 of 169 tests pass; the unchanged Host-only filteredHeaders assertion at tests/network-parsing.test.js:194 fails independently

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

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.

1 participant