[9.x] Document that model encrypter can also be null #45574
Merged
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.
When using a custom encrypter for tests, you need to manually unset the encrypter after use (otherwise it might affect other tests). Since static properties cannot be unset with
unset()
the encrypter needs to be set to null (which is fine because models use??
to use either a custom encrypter or the default).This PR changes the documented type of the custom encrypter so PHPStan allows this: