-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Gradle integration test for wasm-js
and wasm-wasi
targets
#3315
Add Gradle integration test for wasm-js
and wasm-wasi
targets
#3315
Conversation
} | ||
|
||
// HACK: some dependencies (coroutines -wasm0 and atomicfu -wasm0) reference deleted *-dev libs | ||
configurations.all { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You do not need it becase new versions without deprecated dependencies were published.
Please check latest versions here.
# Copyright 2014-2023 JetBrains s.r.o. Use of this source code is governed by the Apache 2.0 license. | ||
# | ||
|
||
dokka_it_kotlin_version=1.9.20-RC2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.9.20 was published. I suggest to use it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
But, what do you think about replacing existing Wasm test instead of creating new one? Wasm is still experimental, and recently in 1.9.20 it started to using latest WasmGC opcodes, so now pre 1.9.20 built binaries will not work in recent browsers and nodejs. And so may be it doesn't make sense to have any tests for them, as eventually it will be deprecated and removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I think the decision to add it as a separate test project is good. The old test that checks that Dokka works with 1.9.10 Wasm doesn't cause any problems, and it will be easy to get rid of if it starts misbehaving or when it's time to drop 1.9.10 support
bb49051
to
cc0af74
Compare
No description provided.