[6.x] Fix auto creating model by class name #33481
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.
I'm targeting
6.x
because it was broken in6.x
by #30653There was an issue about this problem #31180
as @driesvints said
But the thing is
illuminate/database
is only suggestion, not the requirement of this library. Another thing is that https://github.com/laravel-doctrine/ implementsPresenceVerifierInterface
which works perfectly fine.The change that I've proposed does not break anyone else code, it just makes validation rule more general purpose and adds ability for other database ORM providers (the guaranties was given by
PresenceVerifierInterface
, I can implement it on my own and makeFilePresenceVerifier
if my persistence layer is in file, same way I can makeExternalApiPresenceVerifier
and check external API for existence or uniqueness)also saying that
Is not correct, since? as I have described you give
PresenceVerifierInterface