-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[Widget Params] Bug: widget oblivious to updated static value #3379
Comments
@kravets-levko is this something you have time to fix? |
@arikfr @kravets-levko do you think this would do it? a843b92 |
Indeed it will work. I'm just not sure if it solves described issue - it will refresh widget on any parameter mappings change, not only static values 🤔 |
Makes sense anyway, no? If any param changed, refresh visualization. |
Probably yes 🙂 |
@arikfr WDYT? |
I think it makes sense -- like the case where you change a mapping from one dashboard param to another. So as long as it runs when mapping changed, I'm good with this. |
In this pr it refreshes on save button click. Which means, also param label renaming. Would you like to filter that case out? Is refresh such an expensive action that we'd rather avoid any needless calls to it? |
Sometimes it is, sometimes it isn't... If it's easy to call it only when really needed, let's do it. Otherwise, let's fix the bug. |
In my experience this could be a real dealbreaker for trying out the functionality. Some of my dashboards can take north of a minute to update. It feels weird to make changes to the title of a parameter and have it refresh the relevant widgets. Refresh should only happen when absolutely necessary IMO. |
Made it so only parameter value changes trigger an automatic refresh. |
Originally reported by @arikfr in #3334 (comment).
STR:
Expected - Widget auto refreshes with new value.
Actual - Widget remains with previous value.
Clicking the widget refresh button updates it. Just need to make it automatic on change.
The text was updated successfully, but these errors were encountered: