Skip to content
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

API parameter filter_truncate should be applied recursively #2816

Closed
mattab opened this issue Dec 8, 2011 · 1 comment
Closed

API parameter filter_truncate should be applied recursively #2816

mattab opened this issue Dec 8, 2011 · 1 comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Dec 8, 2011

When expanded=1&filter_truncate=3, row truncation (and grouping under "Others") should be applied to the datatable and all children tables.

Typically, we would call Actions.getPageUrls and truncate at 3, to get a full tree view of the pages url structures, while keeping number of rows limited.

This is especially useful for #2137 for Scheduled reports to include recursive views for page urls.

@mattab
Copy link
Member Author

mattab commented Feb 9, 2012

(In [5791]) Fixes #2816

  • filter_truncate now works recursively if the datatable are loaded in memory (ie. expanded=1)
  • Added integration test

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

1 participant