Adam Obuchowicz

@hubertp does GUI attach visualization even if there is no visualization shown under the node (like in the screenshot)?

> > @hubertp does GUI attach visualization even if there is no visualization shown under the node (like in the screenshot)? > > Yes. Then I think there is some...

Ok, I know what happens on GUI side: when record button is pressed and code changed, we invalidate information about method call. Without method call, we actually don't know how...

And visualization update also does not fix the problem. But I assumed #10785 fixes the original issue of double-writes?

* Currently, the Record button is always visible when on, but having it NW would make it a bit odd. * The rerunning a single node is not yet supported...

Refinement notes: * Use the new design for node menu. * Remove "Record" button - leave only "run once". ~~Remove also the handlers for that for the code (like, hiding...

Breaking news: * We actally _want_ to re-introduce record button in the near future, **so don't remove the logic implementation yet**.

Updated the description, loosening somewhat the requirements: as we expect to remove rust build script soon, the new command is optional. Also, after a brief research I discovered https://playwright.dev/docs/api/class-electron -...

I think this should be documented somewhere. [queryClient.clear](https://tanstack.com/query/latest/docs/reference/QueryClient#queryclientclear) says it removes connected _caches_, so I assumed this about it: _cache_ not _query itself_. Also, I would expect that `useQuery` hook...

~~Refinement notes: * The Code Input should always show the picker.~~