I created an EditorAction that writes into a file. I want to provide the user the opportunity to unwrite those changes. I would like to treat those changes as first class objects, and not just Undoables on the undo stack.
What I implemented was a static member ArrayList that holds a reference to those PsiStatements. I could also create a Singleton with the same information.
At any rate, I propose referencing that ArrayList and removing / deleting (however THAT'S done - I know not yet ) each of its contained PsiStatements.
Why is this a bad idea that is going to blow up in my face? Or is it not a bad idea?
Message was edited by: