mirror of
https://github.com/taylanbakircioglu/haproxy-openmanager.git
synced 2026-09-21 01:53:24 +00:00
taylanbakircioglu
82a88ee244
USER QUESTION: "backend içinde aynı durum olabilir mi?"
ANSWER: Yes! Frontend entity has the same issue.
ISSUE SCOPE EXPANDED:
The empty string oldValue problem affects ALL multi-line text fields:
- Backend entity: ✓ Already fixed (options, request_headers, response_headers)
- Frontend entity: ❌ Still using FieldChange component (same bug!)
FRONTEND FIELDS AFFECTED:
- Frontend Options (line 984)
- Request Headers (line 1001)
- Response Headers (line 1018)
- TCP Request Rules (line 1035)
All use FieldChange component → All fail with oldValue = '' (empty string)
SOLUTION: Replace FieldChange with inline rendering for frontend
Applied same pattern as backend:
1. Frontend Options:
- Inline diff rendering
- Badge: NEW/CHANGED based on old value
- Old box: Only if old has content (skips empty string)
- New box: Always shown with green styling
2. Request Headers, Response Headers, TCP Request Rules:
- Same inline pattern
- Badge: CHANGED (orange)
- Graceful empty string handling
CONSISTENCY:
✓ Backend fields: inline rendering
✓ Frontend fields: inline rendering
✓ All text fields handle empty string correctly
✓ No more FieldChange component issues
EDGE CASE HANDLING:
- oldValue = '' → Old box not shown, NEW badge
- oldValue = null → Old box not shown, NEW badge
- oldValue = 'content' → Old box shown, CHANGED badge
RESULT: Complete fix across both backend and frontend entities