angular-ui/ui-grid

Aggregation not updated in tree when using filters

Open

#6,375 opened on Aug 25, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (5,395 stars) (2,496 forks)batch import
good first issueneeds: analysis

Description

Hello,

When using a tree view with filtering enabled and aggregation on a column, the result of the aggregation is not updated when we filter the rows.

This example is forked from the sample 319 Complex Trees, with a COUNT aggregation on the name level. If we filter for example on the age column, the count is never updated Plunkr

Calling refresh() on gridApi does not update the value either, the only way to have the count updated is to rebuild the data, but then all rows are collapsed

In this example, click on the rebuild data button after filtering and the count is updated Plunkr 2

Is this beahviour expected ?

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
AngularJSUI Grid internalstree grid concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Examine the Plunkr examples linked in the issue to reproduce the bug. Look into the ui grid source code for tree view aggregation and filter integration, particularly the gridApi.refresh() method. Investigate whether the aggregation recalculation is triggered on filter change and why it is not updating. Consider if a fix involves listening to filter changes and updating aggregation accordingly. Since no comments exist, verify with maintainers if this is a known issue.