Files
minio-webui/.roo/rules-code/apply_diff_guidelines.md
T
paul a27b405392 fix: Clarify MinIO access credentials in UI
- Update CreateUserDialog labels to show 'Username (Access Key)' and 'Password (Secret Key)'
- Add helper text explaining these are MinIO credentials
- Enhanced success display to show credentials with proper MinIO terminology
- Add MinIO CLI connection examples in credential displays
- Fix confusion about where to get access key and secret key

This addresses user feedback about unclear credential terminology and aligns
with MinIO documentation where username = Access Key and password = Secret Key.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-07-23 17:33:13 +02:00

1.2 KiB

Preventing apply_diff Errors

CRITICAL: When using apply_diff, never include literal diff markers in your code examples

CORRECT FORMAT for apply_diff:

<apply_diff>
  <path>file/path.js</path>
  <diff>
    <<<<<<< SEARCH
    // Original code to find (exact match)
    =======
    // New code to replace with
    >>>>>>> REPLACE
  </diff>
</apply_diff>

COMMON ERRORS to AVOID:

  1. Including literal diff markers in code examples or comments
  2. Nesting diff blocks inside other diff blocks
  3. Using incomplete diff blocks (missing SEARCH or REPLACE markers)
  4. Using incorrect diff marker syntax
  5. Including backticks inside diff blocks when showing code examples

When showing code examples that contain diff syntax:

  • Escape the markers or use alternative syntax
  • Use HTML entities or alternative symbols
  • Use code block comments to indicate diff sections

SAFE ALTERNATIVE for showing diff examples:

// Example diff (DO NOT COPY DIRECTLY):
// [SEARCH]
// function oldCode() {}
// [REPLACE]
// function newCode() {}

ALWAYS validate your diff blocks before executing apply_diff

  • Ensure exact text matching
  • Verify proper marker syntax
  • Check for balanced markers
  • Avoid nested markers