viewers commented on issue #17683:
URL: https://github.com/apache/superset/issues/17683#issuecomment-1374815152
Hi Guys,
I've reproduced the issue on 2.0.1,
It seems that the plugin is called before it finished initialisation.
Looking into the code of
**superset-frontend/./src/explore/components/ExploreViewContainer/index.jsx**,
it looks as we try to triggerQuery on a component that did not complete
loading,
The following fix works, but needs to be checked for side effects.
***************
*** 387,393 ****
control =>
control.validationErrors && control.validationErrors.length > 0,
);
! if (!hasError) {
props.actions.triggerQuery(true, props.chart.id);
}
}, []);
--- 390,396 ----
control =>
control.validationErrors && control.validationErrors.length > 0,
);
! if (!hasError && !isDynamicPluginLoading ) { // If we have a Dynamic
plug in, make sure it finished loading
props.actions.triggerQuery(true, props.chart.id);
}
}, []);
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
