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.

Sign up for GitHub

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

Jump to bottom

Separate observables list of reports in a different QueryRenderer #254

Closed
SamuelHassine opened this issue Oct 13, 2019 · 0 comments
Closed

Separate observables list of reports in a different QueryRenderer #254

SamuelHassine opened this issue Oct 13, 2019 · 0 comments
Assignees
@SamuelHassine
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR) technical improvement Technical refactor or improvement is needed
Milestone
Release 2.0.0

Comments

@SamuelHassine
Copy link
Member

Problem to Solve

If a report has a lot of observables, there is a performance problem at the display because they are all loaded on the overview (fragment loaded).

Current Workaround

None.

Proposed Solution

Implement a specific query renderer for the observables section of a report.

Additional Information

None.
@SamuelHassine SamuelHassine self-assigned this Oct 13, 2019
@SamuelHassine SamuelHassine added feature use for describing a new feature to develop technical improvement Technical refactor or improvement is needed labels Oct 13, 2019
@SamuelHassine SamuelHassine added this to the Release 2.0.0 milestone Oct 13, 2019
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Oct 13, 2019
richard-julien pushed a commit that referenced this issue Oct 15, 2019
@richard-julien
[frontend] Separate observables list of reports in a different QueryR…
18c12ed 
…enderer (#254)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR) technical improvement Technical refactor or improvement is needed
Projects
None yet
Milestone
Release 2.0.0
Development

No branches or pull requests
1 participant
@SamuelHassine