Reproduction link
https://stackblitz.com/edit/thqhof5y?file=src%2Fapp%2Fapp.ts
Steps to reproduce
Launch the existing code and open up the browser console. Click the "Add a column" button and notice how every time this is clicked we get new console log statements from the nzQueryParams event. This event is meant for lazy loading from an API. We have a lot of tables which dynamically hide/show columns based on certain data or that allow users to hide/show columns. Why should each column selection change trigger a lazy load event which would reach for real data from an API? This is just a visual state change and shouldn't trigger lazy load.
What is expected?
Column selections should not trigger the lazy load event
What is actually happening?
Anytime the column collection is modified lazy load is executed.
| Environment |
Info |
| ng-zorro-antd |
21.1.0 |
| Browser |
Chrome |
Reproduction link
https://stackblitz.com/edit/thqhof5y?file=src%2Fapp%2Fapp.ts
Steps to reproduce
Launch the existing code and open up the browser console. Click the "Add a column" button and notice how every time this is clicked we get new console log statements from the nzQueryParams event. This event is meant for lazy loading from an API. We have a lot of tables which dynamically hide/show columns based on certain data or that allow users to hide/show columns. Why should each column selection change trigger a lazy load event which would reach for real data from an API? This is just a visual state change and shouldn't trigger lazy load.
What is expected?
Column selections should not trigger the lazy load event
What is actually happening?
Anytime the column collection is modified lazy load is executed.