While playing with structural search and replace I had a very nice idea:
What if a user can define a new inspection herself by creating a structural search and replace and saving it with an inspection name and description?
Inspection is triggered by search result and automatically offers quick fix, i.e. replace expression.
There could be a bunch of default inspections defined this way, e.g. to replace deprecated JDK code with new construct.
The same way I could define inspections to align code to my own company's standard, e.g. "direct construction of JButton" with quick fix "use com.foo.SwingFactory.createButton()" instead (just a contrived example).
Would this be feasible with the current opan api?