Hey team, could someone please review this PR when...
# infisical-contributing
s
Hey team, could someone please review this PR when you get a chance? Previously, creating a group with an existing slug showed a generic error. Now, after my improvement changes, it returns a specific duplicate-slug message, similar to how sub-organization create/update already works. It improves group slug conflict handling by: • returning a clear duplicate-slug error message on create/update • normalizing user-provided slugs consistently • moving update uniqueness checks into the transaction to avoid race-condition edge cases PR: https://github.com/Infisical/infisical/pull/5798 Thanks a lot!
I ran into this while testing org access management: when creating a group with an existing slug, the UI showed a generic “Something went wrong” toast. That made it unclear what to fix, especially compared to sub-organization create/update, which already returns a clear duplicate-slug message. This change improves UX by returning a specific error for duplicate group slugs, so users immediately know what went wrong and how to resolve it. The scope is intentionally minimal and easy to review: • small backend-only update in
group-service.ts
• no API contract changes • no frontend changes required • behavior is aligned with existing sub-org error handling pattern