You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: The key of a List is included as an element of said list. #1283
It's normal that that happens as part of the serialization process: there should always at some point be an Iterable that mentions the field name and then the value. It should however not get passed to the ListBuilder :)
It works in all the cases I know about ;) so I'll need more information to make any progress here please.
Is there any chance you can provide a small repro of the problem?
Error: Expected a value of type 'Iterable<Object?>', but got one of type 'String'
I'm trying to get a minimal example that I can share with you. Unfortunately, there is a lot I have to prune out.
It should be noted that the error got suppressed somewhere along the line. I had to follow the logic path step-by-step, via IntelliJ Debug, in order to catch it.
Activity
davidmorgan commentedon Nov 28, 2023
It's normal that that happens as part of the serialization process: there should always at some point be an
Iterablethat mentions the field name and then the value. It should however not get passed to theListBuilder:)It works in all the cases I know about ;) so I'll need more information to make any progress here please.
Is there any chance you can provide a small repro of the problem?
Thanks.
jlambright commentedon Nov 28, 2023
I'll need to check on how much I can share.
I should be able to get you the code generated by the OpenAPI Client Generator, as well as a sample of the JSON structure this is happening with.
Sincerely,
TechStop Josh 😉
jlambright commentedon Nov 28, 2023
Error: Expected a value of type 'Iterable<Object?>', but got one of type 'String'
I'm trying to get a minimal example that I can share with you. Unfortunately, there is a lot I have to prune out.
It should be noted that the error got suppressed somewhere along the line. I had to follow the logic path step-by-step, via IntelliJ Debug, in order to catch it.