Repository navigation
Description
Problem and evidence
The maintainer reports that the reuploaded Zoo Code 3.96.0 still receives Plugin Verifier findings: 3 internal API usages, 11 scheduled-for-removal usages, and 10 deprecated usages. This follows #16 and #17; it includes the deliberately retained editor-focus implementation associated with #5 and additional proxy, terminal, and utility migrations.
The new report excerpt does not include the IDE product/build, verifier version, Java runtime, report URL, or uploaded ZIP checksum. Capture these before comparing it with the original IntelliJ IDEA IU-233.15619.7 report in #16. Different targets can annotate the same API differently. The excerpt alone does not establish a binary incompatibility or Marketplace rejection.
Source inspection: commit b3ab5de. Paths below are relative to jetbrains_plugin/src/main/kotlin/org/zoocode/jetbrains/.
Findings and proposed work
| Surface | Reported usages | Current code and migration direction |
|---|---|---|
| Internal editor APIs | FileEditorManagerEx.openFile(...) ×1; FileEditorOpenOptions ×1; withRequestFocus(boolean) ×1 |
editor/EditorAndDocManager.kt:212-225. Find a public asynchronous opening API that preserves chat focus and queued keystrokes. The synchronous opening path previously discarded typing; preserve the #5 regression tests. JetBrains' migration table does not list a replacement for these symbols. Request a supported API in YouTrack if no suitable public API exists. Reflection or suppression is not a resolution. |
| Proxy settings scheduled for removal | HttpConfigurable ×1 and fields PAC_URL, PROXY_EXCEPTIONS, PROXY_HOST, PROXY_PORT, USE_HTTP_PROXY, USE_PROXY_PAC ×1 each |
util/ProxyConfigUtil.kt:61-83. Current upstream deprecation notices explicitly recommend ProxySettings.getProxyConfiguration() for these fields; related APIs include ProxyAuthentication, ProxyUtils, and HttpConnectionUtils. Our code exports settings to the extension host, so replacing this with a JVM HTTP client alone does not solve the actual integration. Check availability in every supported SDK and preserve manual proxy, PAC, exclusions, and IDE-before-environment precedence. |
| Utility methods scheduled for removal | PathEnvironmentVariableUtil.findExecutableInPathOnAnyOS(...) ×1; SystemInfo.getOsNameAndVersion() ×1 |
core/ExtensionProcessManager.kt:387,128. Upstream SystemInfo recommends OS.CURRENT and OS.version(); plain Java system properties are also a candidate for this logging-only use if compatible with the baseline. Confirm the exact upstream replacement for executable lookup against the reported target; preserve Windows executable suffix/PATH behavior and macOS/Linux discovery. No replacement for the PATH helper has been verified in this research. |
| Terminal runner methods scheduled for removal | LocalTerminalDirectRunner.createProcess(...) ×1; createTtyConnector(...) ×1 |
terminal/TerminalInstance.kt:240-290. Upstream directs both deprecated methods to createTtyConnector(ShellStartupOptions). Current code already bridges old and newer signatures because the 2023.3 SDK lacks the newer method. Evaluate separate compatibility implementations or release lines rather than blindly deleting legacy hooks. Preserve the custom PTY connector, cleanup, and focus behavior. |
| Deprecated terminal customizer | LocalTerminalCustomizer ×2; customizeCommandAndEnvironment(...) ×1 |
terminal/WeCoderTerminalCustomizer.kt and its descriptor registration. Upstream explicitly recommends ShellExecOptionsCustomizer.customizeExecOptions(Project, MutableShellExecOptions). Check its API status, availability, and extension-point registration in the actual supported SDKs before adoption. Preserve Bash/Zsh/PowerShell integration and environment/path translation semantics. |
| Deprecated thread IDs | Thread.getId() ×2 |
core/ExtensionSocketServer.kt:128, core/ExtensionUnixDomainSocketServer.kt:111; Kotlin .id emits the getter. JDK documentation recommends threadId() (introduced in Java 19). Current bytecode target is Java 17, so direct migration would break the older runtime. Prefer thread names for these diagnostics if numeric identity is unnecessary, or explicitly decide the minimum runtime first. |
| Deprecated diff access | DiffRequestProcessorEditor ×1; getProcessor() ×1 |
editor/EditorAndDocManager.kt:454-462. Investigate public diff/editor ownership and lifecycle APIs on the target SDK; do not assume a class-name substitution preserves disposal semantics. Exact supported replacement remains to be established. |
| Deprecated editor open | FileEditorManager.openFile(VirtualFile, boolean) ×1 |
editor/EditorAndDocManager.kt:254. Confirm the public replacement and its minimum SDK; verify normal file opens and preserveFocus behavior independently of the internal async path above. |
| Deprecated focus scheduling | IdeFocusManager.doWhenFocusSettlesDown(Runnable) ×1 |
util/TerminalCreationFocusGuard.kt:106. Establish the documented replacement for the target SDK; retain the guard's focus-restoration ordering and project-disposal behavior. |
| Deprecated file-save descriptor constructor | FileSaverDescriptor.<init>(...) ×1 |
actors/MainThreadDiaglogsShape.kt:147. Inspect the precise overload and target SDK deprecation guidance, migrate to its supported construction/configuration API, and verify title, description, file filters, default filename, and cancellation behavior. |
Research-backed implementation policy
- Prioritize internal APIs and removal-marked APIs. JetBrains states internal APIs must not be used by plugins; scheduled-for-removal APIs will be removed. Deprecated APIs require migration planning but do not alone prove binary failure. Verifier and API status guidance.
- Use public replacements and escalate missing ones upstream. JetBrains directs developers to current source documentation and YouTrack when no replacement is available. The editor APIs above are not covered by the migration table. Internal API migration.
- Decide the supported range before adopting new APIs. The project currently builds against platform 2023.3, emits JVM 17 bytecode, and leaves until-build open. JetBrains recommends building against the lowest supported version; separate release branches may be needed when APIs cannot span the range. Do not silently raise the baseline or claim that latest-master APIs work on 2023.3. Build ranges and targeting multiple versions.
- Run Plugin Verifier on the exact distributable in CI, in addition to UI integration tests. Runtime focus tests do not establish static API compatibility. Record the plugin version and ZIP checksum with each report. Verifier CI guidance.
Primary migration sources consulted
Research date: 2026-11-09. Upstream master links describe current guidance and must be checked against the exact target build before implementation.
- HttpConfigurable source and per-field replacement notices:
ProxySettings,ProxyAuthentication,HttpConnectionUtils,ProxyUtils. - JetBrains IDE infrastructure guide: networking helpers and older-version guidance.
- LocalTerminalDirectRunner source: startup-options connector replacement.
- LocalTerminalCustomizer source: shell exec options customizer replacement and remote path considerations.
- SystemInfo source: OS API replacement.
- JDK 21 Thread documentation:
getId()deprecation andthreadId()availability.
Acceptance criteria
- Attach the complete reupload report with IDE product/build, verifier/JDK versions, artifact checksum, and verification date; reproduce against that exact target.
- Document the supported IDE/JDK range and choose a tested compatibility strategy for newer public APIs absent from 2023.3.
- Account for every reported usage above; eliminate internal API references, or link an upstream replacement request and explicitly track the unresolved release constraint.
- Migrate proxy and terminal APIs with coverage for proxy modes/exclusions/precedence and shell integration/process disposal.
- Resolve the remaining utility, thread logging, diff, file-open, focus, and save-dialog deprecations using target-SDK documentation; record any remaining blockers explicitly.
- Run Plugin Verifier against the oldest supported IDE, the exact failing target, and representative supported current IDEs; publish reports for the built ZIP in CI.
- Run existing native typing/terminal/diff focus regressions and appropriate proxy/save-dialog tests. Obtain the live Solheim environment approval when that opt-in suite is used.
- Publish the resulting report and update Address 3.96.0 Plugin Verifier warnings and validate JCEF compatibility across IDE versions #16/fix: remove obsolete API usages and test Zoo Code 3.96.0 in CI #17 with which findings are resolved; do not treat a successful build or UI suite as a clean verifier result.
This issue captures research and follow-up work; no migration implementation or new verifier run has been performed here.
Activity