Use compilerOptions DSL in Kotlin Multiplatform opt-in example
#4928
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`LanguageSettingsBuilder` interface will be deprecated in the future. Instead, it is better to use the existing `compilerOptions` DSL.
sarahhaggarty
approved these changes
Jun 30, 2025
|
Thanks for your contribution @alibagherifam ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The code snippet demonstrating how to opt in to using an API in a Kotlin Multiplatform module currently uses the
languageSettingsDSL. However, its KDoc includes the following note:The
compilerOptionsDSL was introduced in Kotlin 2.0.0 and has been stable since Kotlin 2.1.0.This PR updates the snippet to use
compilerOptions, aligning it with the current recommended approach and avoiding the use of a soon-to-be-deprecated API.