-
Notifications
You must be signed in to change notification settings - Fork 11.7k
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
Table: Fixes table panel gauge alignment #64994
Conversation
You have successfully added a new CodeQL configuration |
// look at the next 100 rows | ||
alignmentFactor = { ...displayValue }; | ||
|
||
for (let i = rowIndex + 1; i < field.values.length; i++) { |
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.
While the comment says to look at the next 100 rows it doesn't. It looks for the whole length. I tried this out with a data that is 200.000 long and I didn't notice performance degradation so maybe we can leave it as it is?
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.
@zoltanbedi good catch, will fix it.
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.
@zoltanbedi fixed
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.
Awesome lgtm!
} | ||
return alignmentFactor; | ||
} else { | ||
// look at the next 100 rows |
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.
// look at the next 100 rows | |
// look at the next 1000 rows |
* Table: Fixes tables guage alignment issues * Removed console.log * Fixing
Fixes #40925
This is a pretty tricky problem to solve without impacting table panel performance, but I think I found a pretty good compromise that should not impact performance much. it does not solve the problem completely, it can still happen but should be much more uncommon to occur.
Before:
![Screenshot from 2023-03-18 15-27-47](https://user-images.githubusercontent.com/10999/226112766-8073ccc1-dd5e-4360-8bc9-9a340b9ba07a.png)
After:
![Screenshot from 2023-03-18 15-37-45](https://user-images.githubusercontent.com/10999/226112767-bf36de89-9e89-4b13-880e-ac79f4e9209a.png)