[9.x] Add support to detect dirty encrypted model attributes #42888
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.
Currently, a model always determines that an encrypted attribute is modified when you fill a model, even if the value that is being encrypted is the same. This is because it compares the encrypted string, which changes every time you encrypt something regardless of whether the encrypted value is the same.
This PR will add support to detect dirty encrypted model attributes.
I wasn't sure if the tests should be part of
EloquentModelEncryptedCastingTest
orDatabaseEloquentModelTest
. If they need to be moved, let me know 🙌🏻This follows up on #38869 and the question from Taylor #38869 (comment).