Migrate js-stubs from kotlin-js to kotlin-multiplatform with target js#1921
Migrate js-stubs from kotlin-js to kotlin-multiplatform with target js#1921robstoll merged 4 commits intorobstoll:mainfrom
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1921 +/- ##
=========================================
Coverage 91.86% 91.86%
Complexity 120 120
=========================================
Files 455 455
Lines 5017 5017
Branches 240 240
=========================================
Hits 4609 4609
Misses 361 361
Partials 47 47
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@ragul-engg thanks for the changes. I think js-stubs was the only project using build-logic.kotlin-js. Could you please check if we can delete gradle/build-logic/dev/src/main/kotlin/build-logic.kotlin-js.gradle.kts |
|
Yeah, will look into that. BTW in console there is a different warning being produced do you have any idea about this ? |
|
Done as you have pointed out the |
The warning is legit as we produce kotlin 1.4 compatible code. However, normally we suppress it. I guess some setup we had in build-logic.kotlin-js is missing now. Thinking about it a bit more, we should not delete build-logic.kotlin-js -- sorry for the wrong suggestion 🙈 |
This rename from main to jsMain directory change is required as part of the plugin migration from kotlin-js to kotlin-multiplatform. More Reference at Step 2 of this doc: https://kotlinlang.org/docs/multiplatform-compatibility-guide.html#migration-from-kotlin-js-gradle-plugin-to-kotlin-multiplatform-gradle-plugin
|
I did base the build-logic.kotlin-js on multiplatform-conventions. I am still seeing the same warning. I don't think we have anything specific to suppress those compileKotlinJs warnings in kotlin-js previously. Dropping the file for reference, I just replaced it to refer the mp-conventions |
|
@robstoll I found out the issue. kotlin-js build logic was lacking the kotlin-conventions, adding that suppressed the warning. |
|
Sounds like I did something wrong, the Multiplattform convention should most likely be based on kotlin-convention as well. Would you like to check? |
|
looks like its just based on just gradle-conventions. should i change that to kotlin-conventions as it imports gradle-conventions anyway. I think it should be fine, what do you think? |
|
I think I missed to adjust it when I introduce kotlin-convention. Please change it, we will get a CI error if our assumption is wrong |
|
Done ✅, lets see whether our assumption is right |
|
Thanks for fixing more than required 🙂 |
resolves #1887
I confirm that I have read the Contributor Agreements v1.0, agree to be bound on them and confirm that my contribution is compliant.