jstuyts / kotlin-multiplatform-recipes Goto Github PK

http://kotlinlang.org/docs/reference/javascript-dce.html

For example I have a project with modules:

• jvm(jvm platform), expectedBy project(':common')
• js(js platform), expectedBy project(':common')
• common(common platform), compile project(':util')
• util(common platform)

Then I want to add tests to util module, but the tests don't appear when i run :js:test. So i want to delegate tests. Thanks.

Kotlin: Modifier 'impl' is only applicable to members that are initially declared in platform-independent code

Took me few times to read README.md to find the way to make build pass.

https://discuss.kotlinlang.org/t/unit-testing-in-kotlin-js/3943

Stick with QUnit, or create examples for all 7 (QUnit, Jasmine, Mocha, Jest, Karma, frontend-plugin, and Tape) test frameworks?

https://discuss.kotlinlang.org/t/multi-platform-project-javascript-unittest/6047/3

Source map rewriting is planned for the DCE tool. Adjust the build if needed when it has been implemented. See: https://youtrack.jetbrains.com/oauth?state=%2Fissue%2FKT-19821

https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/

The syntax for multi-platform code has been changed in 1.2. Instead of header and impl, expect is used: http://kotlinlang.org/docs/reference/multiplatform.html

Create a branch for 1.2, and migrate the code.

Also add a clear warning to the documentation that the code that compiles on the current stable will no longer work from 1.2.

From v0.6 Kotlin/Native supports multi platform projects which can be used for iOS application development. Is Kotlin/Native multi platform project support included in the scope of this project?

The questions asked in #9 is valid, and the project should show how to do this properly. Create a common library, and show how this must be used in another common module, the JavaScript module and the JVM module. Also provide tests for the library module.

The Kotlin API documentation has very nice drop-down menus to select the platform and the API version. This project should show how you can generate the same for your own project. Add API docs to the types, properties and functions, and generate HTML for the API docs in the build.

In your list of Current Issues the path to Delegate IDE build/run actions to gradle is wrong.
It might have changed recently but in 2018.2.4 its in Build, Execution, Deployment >> Build Tools >> Gradle >> Runner