-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
declaration mismatch in laravel 8 #20
Comments
As a workarround I update the declaration inside vendor to: |
Thanks for making this issue. I was looking into whether I could use this in my project. |
I ran into the same issue. @silverax If you need to use the trait and still be able to use the trait in your code, you can use my code below. It 'inherits' the trait and overwrites the
|
I will try that in my next project!!!!! Thanx!! |
Your decision helped me a lot.
|
Declaration of LaravelTreats\Model\Traits\HasCompositePrimaryKey::setKeysForSaveQuery(Illuminate\Database\Eloquent\Builder $query) should be compatible with Illuminate\Database\Eloquent\Model::setKeysForSaveQuery($query)
The text was updated successfully, but these errors were encountered: