Recommended fallback or migration strategy for FileEditorPolicy.HIDE_OTHER_EDITORS (Experimental API)

IntelliJ Platform
,
1

I noticed from the Javadoc that HIDE_DEFAULT_EDITOR recommends using FileEditorPolicy.HIDE_OTHER_EDITORS instead:

However, HIDE_OTHER_EDITORS is currently annotated with @ApiStatus.Experimental.

We are already using FileEditorPolicy.HIDE_OTHER_EDITORS to control editor behavior in our plugin. Given its experimental status, I wanted to check:

  • Is there a recommended fallback or defensive approach we should adopt in case this API changes or is removed in future IDE versions?
  • Are there any plans to stabilize this API, or an alternative non-experimental mechanism we should consider for similar behavior?
  • Would you recommend any version checks or compatibility patterns to safely use this API across IDE updates?

Any guidance on the intended long-term usage or migration strategy would be greatly appreciated.

Removal of deprecated APIs: CefLocalRequestHandler and CefStreamResourceHandler
2

The enum value FileEditorPolicy.HIDE_OTHER_EDITORS exists for so long that we probably will just mark it stable as-is in one of the next releases, we have no any plans to change it in the future.

3

Thank you for your immediate response @yuriy.artamonov