Create a test case to reproduce the typealias lambda issue in KSP2 #85
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.
Based on the section in FORK.md, we're trying out KSP2 with Dagger kapt, and we ran into this error:
It's caused by typealias lambda, attaching the code snippet
I'm not sure where the issue resides, it's either on the KSP side or Anvil, but I couldn't find a relevant issue about typealias lambda in KSP repo. I went through the
AssistedFactoryGeneratorTest
, and I didn't see any test cases related to typealias lambda parameter, so I added one test case. Although it's passing currently, I think maybe it's still worth having it for #22?