11.0 release #107
Closed
11.0 release #107
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
…uch easier to expand on additional features and testing.
…velopers to setup their query logs.
kontoulis
suggested changes
Jan 23, 2024
There was a problem hiding this comment.
@kirkbushell this is very nice PR, with attention to detail and the new implementations are really good! The code comments helped me a lot while going through it.
I left some comments about typos, some improvements in terms of simplification and readability, and a couple of questions, but everything seems well-thought and I couldn't find any significant issues 🙂
I am really looking forward for this to go out!
P.S. I finally am aware of all the capabilities of this amazing package!
|
Moving to release branch. |
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.
Currently work in progress, but this PR encapsulates the complete rework of the Eloquence solution, using a much nicer and workable API with modern approaches.
The main objective of version 11 is to prepare for Laravel 11 (in general), whilst introducing a nicer API and easier way of working with the main camelcasing trait, and providing better support for its various data aggregation features.
Due to the amount of changes, backwards compatibility is not possible.
Upgrade guide to come.