SECRETS-116 Improve error handling for large secret value imports

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Overview

Greptile Summary

Fixed validation error when renaming newly created secrets by addressing skipMultilineEncoding null handling.

Root cause: Newly created secrets could have skipMultilineEncoding set to null. When renaming these secrets, the frontend was sending the full secret payload (including skipMultilineEncoding: null) to the PATCH endpoint, which only accepts boolean or undefined, causing validation errors.

Solution implemented:

• Frontend rename forms: Removed unnecessary fields (tagIds, secretComment, secretReminderRepeatDays, secretReminderNote, skipMultilineEncoding) from rename requests, sending only required fields plus newSecretName
• Frontend mutation hook: Added type guard to only send skipMultilineEncoding when it's explicitly a boolean value (converts null to undefined)
• Backend CREATE endpoints: Updated Zod validation to accept null for skipMultilineEncoding and transform it to false
• Backend service layer: Added null coalescing (?? false) throughout secret creation and bulk update operations to ensure skipMultilineEncoding is never persisted as null

Additional changes: Fixed grammar in error message "Shared secret value too long" → "Shared secret value is too long"

The fix maintains backward compatibility while preventing the validation error. PATCH endpoints remain strict (boolean/undefined only), while CREATE endpoints are more lenient (null → false).

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix correctly addresses the validation error by handling null values at multiple layers (frontend and backend). The approach is conservative - removing unnecessary fields from rename operations and adding defensive null coalescing. No breaking changes to the API contract.
• No files require special attention

Important Files Changed