# DocumentUpdatingActionOnSave was made internal, but is public API **URL:** \ **Category:** IntelliJ Platform\ **Created:** [June 22, 2026, 8:30pm UTC](https://platform.jetbrains.com/t/documentupdatingactiononsave-was-made-internal-but-is-public-api/4532 "2026-06-22T20:30:42Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![nik](https://sea1.discourse-cdn.com/flex001/user_avatar/platform.jetbrains.com/nik/32/65_2.png) [@nik](https://platform.jetbrains.com/u/nik)\ **Post date:** [June 23, 2026, 7:32am UTC](https://platform.jetbrains.com/t/documentupdatingactiononsave-was-made-internal-but-is-public-api/4532/3 "2026-06-23T07:32:28Z")
Hi Joachim! I’ll restore visibility of `ActionOnSave` ([IJPL-248128](https://youtrack.jetbrains.com/issue/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](https://platform.jetbrains.com/t/2026-2-eap7-smartelementdescriptor-was-made-internal-but-is-superclass-of-public-api/4501/3)) usages weren’t found. I’ve already added some internal checks to help us not to repeat such mistakes. --- _[View the full topic](https://platform.jetbrains.com/t/documentupdatingactiononsave-was-made-internal-but-is-public-api/4532)._