[Feature]: Whenever code bound to a widget data field is run, it should take the widget into a loading state.

[satbir121]

Is there an existing issue for this?

• [X] I have searched the existing issues

Summary

Currently, if an Api or a Query is bound to a widget's data field, and the API/Query is run, the widget is taken into loading state. The Widgets do not go into a loading state when a JS Object function is bound to the data field.

Expected behaviour is for the Widgets to go into a loading state when:

1. Any JS object function bound to a data field is executing.
2. Any code written inside the data field property is executing.

Why should this be worked on?

We should work on this to maintain consistency in the loading behaviour when a API, Query and JS object function is bound to a data field.

[codenameakshay]

Same use case, need to animate loading in the table when the data is being fetched from the TestDetails.onSelectEval() method.

[codenameakshay]

This also doesn't works with charts. This is a major issue, as users don't understand when data is loading, and hence they think that there is an error, as chart shows No chart to display message instead of empty or showing any loader.

[avjaintwilio]

I have the same issue with the table not going into loading mode when a JS object is called to populate the data. It makes it look like the table is already loaded, when the table has old data from the previous input. This is confusing for the user as it shows the stale data in the table without giving the user a signal for new data loading.

[rishabhrathod01]

@rahulbarwal We could also note this issue down when we plan to fix the widget loading related issues.