Closed bgevko closed 3 months ago
The issue wasn't from the class objects, but it turns out, those were causing an unrelated issue with state updates. The hot reloading issue came from not naming my hooks in CamelCase.
I did end up backing out of class-based state, as it was too complicated to manage correctly, and I did rename the conflicting modules. This seems to have fixed the issue.
When saving changes, sometimes Vite doesn't hot reload.
The issue is likely coming from
ProcessNode
,FileNode
, and/orFileSystemTrie
class objects.Re-examine how the inner methods are updating the state and make sure that Zustand is aware of all state changes.