Add UniqueWithTrashed validation rule #6659
Closed
+10,686
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You can use Rule::unique for this. |
The built-in unique rule does not automatically ignore soft-deleted records. This means if a record exists with a non-null deleted_at, the default unique validation would still fail. My UniqueWithTrashed rule automatically ignores soft-deleted items, making it easier to enforce uniqueness only among active records without repeating custom query logic each time. It’s especially helpful in applications that heavily use soft deletes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new custom validation rule UniqueWithTrashed that allows developers to enforce uniqueness of a column while ignoring soft-deleted records (deleted_at is not null).
Why it’s useful:
Laravel’s built-in unique rule doesn’t ignore soft-deleted rows by default.
This rule allows for cleaner validation logic in applications that use soft deletes.
Usage Example:
This checks that the name column in the zones table is unique, excluding any soft-deleted rows.