Accept files from any placeholder key

[Giardi77]

Summary by CodeRabbit

• Refactor
  • Improved configuration payload processing to handle all payload types uniformly instead of a single specific type.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The code refactors payload processing in config.go to generalize from handling a specific "word" key to iterating over all payload keys uniformly. Each payload key is now processed identically by preserving non-existent files and reading/splitting contents from existing files.

Changes

Cohort / File(s)	Change Summary
Payload Processing Generalization config.go	Replaced targeted cfg.Payloads["word"] processing with a generalized loop over all payload keys. Each key is now updated in-place with processed file contents (preserved as-is if non-existent, or split into fields if readable). Error handling for file reads remains unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A loop now embraces each payload with grace,
No special treatment for words in this place,
All keys are equal in this generous span,
Refactored with care—a most elegant plan! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Accept files from any placeholder key' directly and clearly describes the main change: replacing targeted processing of a single payload key with generalized processing of all payload keys.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 360f604 and 5462b86.

📒 Files selected for processing (1)

• config.go

🧰 Additional context used

📓 Path-based instructions (1)

**/*.go

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.go: Use gologger for all logging output instead of fmt.Println
Follow Go naming conventions and project structure for code organization

Files:

• config.go

🔇 Additional comments (2)

config.go (2)

36-37: LGTM! Good generalization.

The refactoring to process all payload keys instead of hardcoding "word" aligns well with the PR objective and makes the code more flexible.

---

38-52: Code is correct as implemented - no changes needed.

The payload processing behavior in lines 40-48 is both correct and consistent with the existing codebase. The two implementation patterns you identified are intentional:

1. Non-existent file paths are preserved as literal values — This matches the identical pattern used in internal/runner/runner.go:133 and correctly allows both file-derived and literal payload values.

2. strings.Fields splits by any whitespace — This is correct for the wordlist use case. Payloads are individual words that get substituted into templates (via Replace() in mutator.go:395), and splitting by whitespace ensures each word becomes a separate payload value, which is the intended behavior for domain permutation generation.

This implementation is consistent with the existing codebase and follows the design patterns already established.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[tarunKoyalwar]

@dogancanbakir