Getting the annotation processor working when I'm using kotlin, gradle and kapt.#75
Merged
andreaTP merged 1 commit intoJun 29, 2026
Conversation
Contributor
|
I agree the current implementation is too restrictive. Do you mind removing the wildcard import to get CI green? |
b23c689 to
074f527
Compare
andreaTP
approved these changes
Jun 29, 2026
andreaTP
left a comment
Contributor
There was a problem hiding this comment.
LGTM, thanks for taking the time to improve it!
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
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.
Hi there,
I has having trouble getting @WasmModuleInterface working with my Kotlin class.
After a bit of digging turns out it was mainly a maven/gradle difference with the assumptions about where resources are placed.
The fix is simply to make WasmModuleProcessor a bit more generous about where it will look for the wasm file.