-
Notifications
You must be signed in to change notification settings - Fork 19
[DON'T MERG - TEMP COMMIT] IBX-10186: Added limits to repository child count queries and subtree operations #1815
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
base: main
Are you sure you want to change the base?
Conversation
0926a1a to
6596463
Compare
3910b82 to
28628a2
Compare
28628a2 to
4e34452
Compare
|
| $currentScope, | ||
| $scopeSettings['subtree_operations']['copy_subtree']['limit'] | ||
| ); | ||
| if (isset($scopeSettings['subtree_operations']['copy_subtree']['limit'])) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those changes should be reflected in Ibexa\Tests\Bundle\AdminUi\DependencyInjection\Configuration\Parser\SubtreeOperationsTest.
| ->children() | ||
| ->integerNode('limit') | ||
| ->info('Limit the total count of items queried for when calculating the the number of direct children a node has. -1 for no limit.') | ||
| ->isRequired() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We cannot "require" this node, as we have defaults declared outside of configuration processing.
With this require, if query_subtree element is added, limit has to be declared regardless if you want to change the limit in a specific site-access or not.
| ->isRequired() |



Related PRs:
#1605
ibexa/core#696
Description:
This one is a community contribution from @ryanolee 🎉 .
This pull request introduces performance optimizations for repository operations by implementing limits on child count queries and subtree operations.
More info here:
#1605
For QA:
See orginal PR
Documentation:
New configuration of limits added