dd-bot | 将B站主播的动态和直播提醒推送至QQ群，基于 nonebot 开发 | Chat library

Edit: I'm attempting to manually use the grid api destroy function in the re-usable component and the parent component actually calling ag grid (in the template). Still having an issue with ag-grid retaining the old data.

I'm using a re-usable component for our app (it's got 50 some odd tables, so we've wrapped up the tooling so it's easier to update/change). I've coded in some filter persistence and row persistence (so if you click on an item, navigate to details, and come back, it'll take you back to that item and have it selected. Useful for our very large grids)

The issue is that when I go from one component where I didn't set the getRowNodeId callback to one where I do, it's freaking out saying there's duplicate node ids (b/c it's still referencing the data from the old grid. The property doesn't exist in that data set so everything is null).

I've tried manually destroying the instance of aggrid onDestroy, but that didn't seem to do anything. I've tried setting the row data to an empty array on init, but that seems to have broken the init logic (I have some logic for first data draw) and in general the initial loading logic for ag grid seems to decide it's done immediately. The persistence logic no longer works if I do this. I've also tried delaying setting that callback until after the first data draw, but then it doesn't seem to use the callback.

Any thoughts on how to keep the getRowNodeId from spazzing out while ag grid resolves the new grid data? (or clear the previous instance of ag grid properly. It seems it's retaining the reference to it somewhere.)

How the grids are setup