Skip to content

Centralize compiler plugin configuration transport - #262

Open
SunsetWan wants to merge 1 commit into
rickclephas:masterfrom
SunsetWan:fix/configuration-contract
Open

SunsetWan wants to merge 1 commit into
rickclephas:masterfrom
SunsetWan:fix/configuration-contract

Conversation

@SunsetWan

Copy link
Copy Markdown

Summary

  • Centralize compiler plugin option encoding in a single Gradle-side configuration contract shared with IDEA import.
  • Preserve compatibility with legacy tooling models while keeping the public model API unchanged.
  • Deprecate the no-op fileSuffix property left behind by the removed source-generation implementation.

Motivation

Gradle compilation and IDEA import independently encoded the same compiler options, including defaults, nullable suffixes, generated source directories, and the Swift export mask. This made configuration changes easy to apply incompletely.

The Gradle plugin now owns the canonical serialized option map. IDEA import reads that contract through its Gradle tooling boundary and retains the previous field mapping only as a fallback for older Gradle plugin versions.

Compatibility

  • Public API signatures and ABI dumps remain unchanged.
  • fileSuffix remains binary- and source-compatible, but now emits a deprecation warning because generated declarations no longer have source file names.
  • Existing tooling model getters continue to work.
  • Older Gradle plugin versions continue to use the legacy IDEA import path.

Testing

  • :kmp-nativecoroutines-gradle-plugin:check
  • -PbuildType=IDE_PLUGIN :kmp-nativecoroutines-idea-plugin:check
  • -PbuildType=COMPILER_TESTS :kmp-nativecoroutines-compiler:check
  • -PbuildType=COMPILER_TESTS :kmp-nativecoroutines-compiler-embeddable:check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant