v3 support for Laravel 11 #739
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey @rubenvanassche Is it possible to merge this? We do not yet want to upgrade to v4. Due to some major changes and also that there are concerns for performance: #730 Thanks! |
|
Thanks for the PR, I'm going to merge this but be sure to update to data v4 this year, we'll probably won't do a Laravel 12 upgrade for v3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We are stuck on laravel-data v3 for a little while longer but are attempting a Laravel 11 upgrade. This PR allows us to continue using laravel-data with the latest version of Laravel.