Skip to content
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

handle explicit return type unit properly #63

Closed
marc0olo opened this issue Jul 6, 2021 · 1 comment · Fixed by #68
Closed

handle explicit return type unit properly #63

marc0olo opened this issue Jul 6, 2021 · 1 comment · Fixed by #68
Assignees
Labels
bug Something isn't working
Projects

Comments

@marc0olo
Copy link
Member

marc0olo commented Jul 6, 2021

it seems like if unit (similar to void) is explicitely defined as return type of an entrypoint the generated return type is Pair<String, Object> instead of the expected String

@mitch-lbw
Copy link
Member

The issue might be in different aci results from methods explicitely declaring unit as return type and methods which don't

@mitch-lbw mitch-lbw added this to To do in v2.0.0 Jul 13, 2021
@mitch-lbw mitch-lbw self-assigned this Jul 13, 2021
@mitch-lbw mitch-lbw moved this from To do to In progress in v2.0.0 Nov 3, 2021
@mitch-lbw mitch-lbw linked a pull request Nov 3, 2021 that will close this issue
mitch-lbw added a commit that referenced this issue Nov 4, 2021
@mitch-lbw mitch-lbw moved this from In progress to Done in v2.0.0 Nov 4, 2021
@mitch-lbw mitch-lbw added the bug Something isn't working label Jan 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
v2.0.0
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants