-
Notifications
You must be signed in to change notification settings - Fork 1.4k
hasOne no longer compatible with latest Laravel #63
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
Comments
Don't really know if I should change this now, or wait for the stable 4.1 release ... |
@jenssegers, you could have a seperate branch that points to the development version of Laravel 4.1, so that people working on Laravel 4.1 could use that branch to take advantage of all the new changes of Laravel 4.1. The master and the tags can still point to 4.0 |
A separate dev-type branch like @abishekrsrikaanth suggested that just maintains compatibility would be great. A lot of these things can just be fillers initially, I'd just rather not maintain my own fork to avoid simple errors. |
I agree with @abishekrsrikaanth and @WMeldon on this. This will be very helpful. |
The last commit on the develop branch updates some methods to their 4.1 version: 257b92f Can you test this version? |
Works like a charm. Thanks @jenssegers . I'll be back as soon as Taylor adds another method parameter to Eloquent :D |
As of this change, errors are thrown due to method incompatibilities.
The text was updated successfully, but these errors were encountered: