fix: AI Text Generator Block prompt value handling

[chojuninengu]

When using the AI Text Generator block, users were unable to create prompt values with similar names (e.g., 'PR-Title' and 'PR-Title-test') as the second value would be instantly removed. This restricted users from specifying prompt variables whose names overlap, which is important for thorough testing and differentiating prompt roles. The fix allows for more flexible naming while still preventing exact duplicates.

Changes 🏗️

• Modified NodeKeyValueInput component to only check for exact duplicates
• Added validation to prevent exact duplicate keys while allowing similar key names
• Preserved values when updating keys
• Improved key input handling logic in the component

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • Create a new AI Text Generator block
  • Add a prompt value with key 'PR-Title'
  • Add another prompt value with key 'PR-Title-test' (should work now)
  • Add a prompt value with key 'PR-Title' (should be prevented as exact duplicate)
  • Edit existing prompt value keys to ensure values are preserved
  • Verify that similar but non-identical keys are allowed
  • Test with multiple prompt values to ensure all functionality works as expected

For configuration changes:

• .env.example is updated or already compatible with my changes
• docker-compose.yml is updated or already compatible with my changes
• I have included a list of my configuration changes in the PR description (under Changes)

Fixes #9884

[CLAassistant]

All committers have signed the CLA.

[github-actions]

This PR targets the master branch but does not come from dev or a hotfix/* branch.

Automatically setting the base branch to dev.

[deepsource-io]

Here's the code health analysis summary for commits d5dc687..6cd15cc. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success	❗ 21 occurences introduced 🎯 18 occurences resolved	View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 9884 - Fully compliant Compliant requirements: • Fix bug where prompt values with similar names (e.g., 'PR-Title' and 'PR-Title-test') are removed • Allow users to define multiple prompt values with unique names, even if one is a substring of another • Still prevent exact duplicate names

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Validation Timing The duplicate check is performed after user input, but there's no visual feedback to users when a duplicate key is rejected. Consider adding user feedback when duplicates are detected. // Check for exact duplicates only const hasExactDuplicate = newPairs.some((pair, index) => newPairs.findIndex(p => p.key === pair.key) !== index ); if (!hasExactDuplicate) { setKeyValuePairs(newPairs); handleInputChange( selfKey, newPairs.reduce((obj, { key, value }) => ({ ...obj, [key]: value }), {}), ); }

[netlify]

✅ Deploy Preview for auto-gpt-docs ready!

Name	Link
🔨 Latest commit	6cd15cc
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/6810f81fd958f40008403b6b
😎 Deploy Preview	https://deploy-preview-9896--auto-gpt-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev ready!

Name	Link
🔨 Latest commit	6cd15cc
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/6810f81f9fb8810008a286a2
😎 Deploy Preview	https://deploy-preview-9896--auto-gpt-docs-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ntindle]

Screen.Recording.2025-04-30.at.8.53.00.AM.mov

[ntindle]

still seeing behavior, see attached video