You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Almost all components that use imx-data-table or imx-data-source-toolbar call their GET endpoint twice.
Cause explained using the example of identities.component:
In the OnInit of the components, navigate is called. This triggers the GET endpoint. Then, the DataSourceToolbarComponent.updateNavigateStateWithFilters emits navigationStateChanged again, causing navigate to be called once more and thus the GET endpoint is triggered again.
Among other things, the dataSourceHasChanged check in DataSourceToolbarComponent.ngOnChanges doesn’t seem to fit. I suspect it should be something like this:
We ended up adding a dirty workaround in navigate where it skips calling getAllPersonAdmin/getReportsOfManager and instead just passes an empty data object to this.dstSettings.dataSource the first time it's called after the component is created.
Having a fix for DataSourceToolbarComponent itself that would fix it for all views would be preferrable.
Almost all components that use imx-data-table or imx-data-source-toolbar call their GET endpoint twice.
Cause explained using the example of identities.component:
In the OnInit of the components, navigate is called. This triggers the GET endpoint. Then, the DataSourceToolbarComponent.updateNavigateStateWithFilters emits navigationStateChanged again, causing navigate to be called once more and thus the GET endpoint is triggered again.
Among other things, the dataSourceHasChanged check in DataSourceToolbarComponent.ngOnChanges doesn’t seem to fit. I suspect it should be something like this:
However, that does not seem to be the root cause.
The text was updated successfully, but these errors were encountered: