Eloquence 11.0 #112
Merged
Eloquence 11.0 #112
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
approved these changes
Jan 31, 2024
I'll add a linter - ty :) |
|
@kontoulis Done. |
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.
Eloquence has had a major overhaul, implementing incompatible API changes with previous versions.
11.0 sees the package move heavily toward PHP attributes as a form of meta-programming to describe how relationships interact with one another for custom behaviours, namely for aggregate value caching (such as counts, sums.etc.).
Due to this, all implementors should take time to review the changes and update their code to the new APIs, which empower developers to implement these behaviours directly as part of their relationship logic.