-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
More accurate tuple types #1139
Comments
Hey @jonaslagoni , Currently when i try to generate the List using KotlinFileGenerator it always generates with List. Does this enhancement fixes that issue? |
What types are you expecting for tuples in Kotlin @janachinna? |
@jonaslagoni Instead of Any, it should use the type mentioned in the async spec file. Eventhough the items spec is referring to a schema object it always generates
This should generate |
@janachinna ahh, yea that's a bug that #1140 is fixing, it will be released as part of v2. To work around this bug you could do this:
|
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Reason/Context
Say we have this:
It would currently generate this:
But the more accurate type would be this:
I think we should be able to define tuple models with additionalItems, so that each output can decide the most accurate representation it can do. For example, in most languages, it would probably be just a generic array type, but in others where possible, they can be as precise as possible.
The text was updated successfully, but these errors were encountered: