Vue destroys the page cards with a large amount of data.

the current project uses vue and element to do, and finds a problem. After entering the current page, it will request an interface with 3000 + pieces of interface data, and then send the data to element-ui to render the select, (page rendering will not card). When the page is loaded, switching other routing discovery will be stuck on the current page, and it will jump after a while. However, the life cycle of the page executes beforeDestroy, but does not perform destroyed,. It means that it is stuck between the two (if you comment out the interface of 3000+ just now, it will not be stuck). Has any boss ever encountered this kind of problem?


according to reason, it should be a rendering time card. Did you report that wrong


Unfortunately, there are obvious stutters when I click on the drop-down when I click on 300 entries

considering that this design itself is unreasonable, 3000 pieces of data are thrown from the back end to the front end at one time, and it is impossible for the user to choose one, so it is better to change to the solution of remote-search

.

Hello, landlord, have you solved this problem?

Menu