| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Dokka has its own documentable model to represent analyzed code. The analysis is performed by a compiler frontend.
In K1 the compiler frontend has descriptors that use the underlying Binding Context (global shared stateful structure). Dokka just maps descriptors to Documentable by DefaultDescriptorToDocumentableTranslator.
K2 compiler has FIR tree, which means “Frontend Intermediate Representation”, instead of Binding Context. But we do not use FIR in Dokka directly, since it is too low-level for analysis. The Kotlin compiler provides high-level Analysis API for this case. The API is used by KSP too. Analysis API represent elements of FIR (declarations, parameters and so on) as Symbols. For more details see KtSymbolByFirBuilder, KtSymbol.
For Dokka symbol is the replacement of descriptor in K2.
Also, to set up the environment of project analysis in K1 we use idea dependencies (or copy-past from there). In K2 for these aims, there is a Standalone mode for Analysis API.
|
|
* Update Kotlin Gradle Plugin to 1.9.0
* Update Android Gradle Plugin to 4.2.2
* Introduce convention plugin for Gradle runner
https://github.com/gradle/gradle/issues/8301
* Fix unit test `common, jvm and macos source sets with kotlin multiplatform`
* Update compiler to 1.9.0
* Update integration test
* Add empty target for WASM integration test to avoid single target project
See https://github.com/Kotlin/dokka/issues/3038
* Remove unused `plugins.shadow` from toml
|
|
|
|
* Get rif of IDE plugin dependencies
Everything in this commit has been copy-pasted from IDE plugin and marked as internal
|
|
* Extract analysis into separate modules
|
|
|
|
|
|
|
|
* Update KGP to 1.8.20
* Update AGP to be compatible with KGP
* Replace `AndroidSourceSet`
* Dump API
* Update integration tests
* Update GH actions tests
* Refactor Gradle Runner
* Fix `TYPE_MISMATCH_WARNING_FOR_INCORRECT_CAPTURE_APPROXIMATION`
* Suppress source sets without compilations
Dokka suppresses source sets that do no have compilation since such configuration is invalid, it reports a warning or an error
* Introduce `dependsOn` for a new `com.android.build.api.dsl.AndroidSourceSet`
* API dump
* Add comment
* Suppress remaining `TYPE_MISMATCH_WARNING_FOR_INCORRECT_CAPTURE_APPROXIMATION`
* Add comment
---------
Co-authored-by: Ignat Beresnev <ignat.beresnev@jetbrains.com>
|
|
* Reorder dependency versions for update convenience
* Try to add more consistency to naming
|
|
|
