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
Fix grouping grid sorting - ACL grids #16529
base: 3.x
Are you sure you want to change the base?
Conversation
Remove stale lines brought in during rebase
Formatting, var naming, and other stylistic changes only; no functional changes.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## 3.x #16529 +/- ##
============================================
- Coverage 21.57% 21.52% -0.06%
- Complexity 10566 10603 +37
============================================
Files 561 561
Lines 31940 32030 +90
============================================
+ Hits 6892 6895 +3
- Misses 25048 25135 +87 ☔ View full report in Codecov by Sentry. |
added later in the getData method. | ||
*/ | ||
switch ($gridCategory) { | ||
case 'usergroup-acl': |
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.
Should this logic be in the generic GetListProcessor or something ACL related?
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.
I chose the placement of the logic based on looking to support other grouping grids down the road (e.g., the Settings one [which could use some work as mentioned in the opening comments], or any Extras that might make use of that type of grid). That said, let me know if you think there's a more appropriate place; perhaps a new processor extending the main GetListProcessor.
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.
@Mark-H - Hey, it's been a while since you made this comment; let me know what your thoughts are on my response above... Thx ;-)
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.
If there needs to be an extra hook in the base getlist processor I don't have objections to that, but I do still think it's kinda weird to have a switch with values for specific implementations in a base class. That just seems like it's not architected properly.
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.
I agree it's not ideal; honestly there's a fair amount of wonkiness in the arch of the processors in general (e.g., there's inconsistency in how get data is handled [ two ways that I've come across ]) that makes it difficult to keep things DRY.
I can take a look at adding an intermediate class if you prefer.
What does it do?
Adds new grouping logic to ACL GetList processors and config props in the corresponding Ext grid classes.
Why is it needed?
Aside from the Settings grid,* other grouping grids (such as the ACL ones) neither group properly, nor sort within groups properly.
How to test
Related issue(s)/PR(s)
No related issue.