Use correct KType when custom InputValue is provided #143
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.
When a custom InputTypeDef is provided, the kqlInput is correctly set, but the inputType is not.
Due to kotlins reflection behaviour, which returns functions with generic types instead of the underlying types, overriding the input type seems mandatory. https://youtrack.jetbrains.com/issue/KT-42746
Doing so enables the use of generics discussed in #139
Example: