It’s a relatively small, simple plugin. Although, we do have some custom logic for packing a Java agent into the plugin (outside of the lib dir) which gets loaded in the bootclasspath later at runtime.
I’m not sure, but you could also clarify this point during a session: is the buildSearchableOptions function really useful?
It can be slow (ho, and I see the ide-perf plugin also disabled it, I’m not alone ) and can be a bit unstable at times, but is it really useful? If my understanding is correct, it indexes all Swing components, and this index can be reused when using the search field in File > Settings. But… this search field returns the same results even without the buildSearchableOptions JAR file.
Thx