To implement „format on save“, the abstract class ActionsOnSaveFileDocumentManagerListener.DocumentUpdatingActionOnSave is extended.
But the outer class of it was made internal recently, which breaks the public API based on nested classes. Plugin verifier complained on the Marketplace.
In regard to API, this eap cycle is really bad. A lot of API is made internal even though there are obvious uses and extensions using it. I‘m feeling very frustrated with it right now…
I’ll restore visibility of `ActionOnSave` (IJPL-248128), thank you for reporting!
In regard to API, this eap cycle is really bad. A lot of API is made internal even though there are obvious uses and extensions using it.
I’m sorry for that. When I was adding @ApiStatus.Internal annotation, I used information about usages from existing plugins on the Marketplace to avoid such problems. However, it appears that some corner cases (an inner class that has usages like here, or usages of inherited methods like in this case) usages weren’t found. I’ve already added some internal checks to help us not to repeat such mistakes.
The new IntelliJ IDEA 2026.2 EAP 8 should restore visibility for the cases reported by you. Also, I processed all other classes that were recently marked as internal and fixed a few other cases where they can be indirectly used via outer classes or subclasses. If you found something that is not fixed, please tell us about that. Thank you!